Forming of an Akka.Cluster is not working anymore after upgrading to 0.3.0-beta1 of Akka.Discovery.Azure

[wesselkranenborg]

Version Information
Akka.Discovery.Azure 0.3.0-beta1
Akka.Cluster 1.4.43

Describe the bug
The Akka.Cluster is not being formed.

To Reproduce
Have a working version of the code running with 0.2.5-beta4, upgrade to 0.3.0-beta1 without code changes and it will not form a cluster again (have tested it in Azure Container Apps)

Expected behavior
To form a cluster.

Actual behavior
In the logging I get the following logrules:

[22/10/10-03:21:28.8920][akka.tcp://service@10.250.1.19:12552/system/bootstrapCoordinator][akka://service/system/bootstrapCoordinator][0042]: Looking up [Lookup(service, , tcp)]
[22/10/10-03:21:28.8992][akka.tcp://service@10.250.1.19:12552/system/bootstrapCoordinator][akka://service/system/bootstrapCoordinator][0006]: Located service members based on: [Lookup(service, , tcp)]: [ResolvedTarget(, 18558, 10.250.0.200), ResolvedTarget(, 18558, 10.250.1.19), ResolvedTarget(, 18558, 10.250.1.38)], filtered to []
[22/10/10-03:21:28.9326][SelfAwareJoinDecider (akka://service)][akka://service/system/bootstrapCoordinator][0035]: Discovered [0] contact points, confirmed [0], which is less than the required [1], retrying
[22/10/10-03:21:29.0573][SelfAwareJoinDecider (akka://service)][akka://service/system/bootstrapCoordinator][0030]: Discovered [0] contact points, confirmed [0], which is less than the required [1], retrying
[22/10/10-03:21:29.3729][SelfAwareJoinDecider (akka://service)][akka://service/system/bootstrapCoordinator][0038]: Discovered [0] contact points, confirmed [0], which is less than the required [1], retrying

Additional context
After downgrading from 0.3.0-beta1 to 0.2.5-beta4 it started to work again.

[Aaronontheweb]

Thanks @wesselkranenborg - we'll look into this right away

[Arkatufus]

This is caused by a bug in ClusterBootstrapSettings because it is getting the wrong Akka.Management fallback port, causing cluster bootstrap to filter out contact points.
For now, you can use this as a workaround to bypass the erroneous contact point filtering:

builder.WithClusterBootstrap(setup =>
{
    setup.ContactPoint = new ContactPointSetup
    {
        FilterOnFallbackPort = false,
    };
});