Network detection on controller is not working

Development
1

Fresh installation of maas on fresh installation of Ubuntu 22.04.

On the controller the ‘fabric-*’ are not (automatically) detected.

The following error logs appear in the maas regiond.log

2023-03-30 07:37:15 provisioningserver.utils.services: [warn] Couldn't report test results: HTTP error [403]
2023-03-30 07:37:39 maasserver.regiondservices.active_discovery: [info] Active network discovery: Active scanning is not enabled on any subnet. Skipping periodic scan.
2023-03-30 07:37:39 twisted.internet.defer: [critical] Unhandled error in Deferred:
2023-03-30 07:37:39 twisted.internet.defer: [critical] 
        Traceback (most recent call last):
        Failure: twisted.internet.error.MulticastJoinError: (b'\xe0\x00\x00v', b'\xc0\xa8z[', 98, 'Address already in use')

Digging through the source, IMHO this is the place where the error is logged:

maas/src/provisioningserver/utils/services.py:1181
in function _updateInterfaces

The underlying problem looks to be:

[pid  4533] setsockopt(13, SOL_IPV6, IPV6_ADD_MEMBERSHIP, {inet_pton(AF_INET6, "ff02::15a", &ipv6mr_multiaddr), ipv6mr_interface=if_nametoindex("enp1s0")}, 20) = -1 EADDRINUSE (Address already in use)
[pid  4533] setsockopt(13, SOL_IP, IP_ADD_MEMBERSHIP, {imr_multiaddr=inet_addr("224.0.0.118"), imr_interface=inet_addr("192.168.122.91")}, 8) = -1 EADDRINUSE (Address already in use)

maas 3.3.1-13169-g.94920eb1e 26658

Any hint?

2

Looks that this was already discussed - but without a clear reason and solution;

https://bugs.launchpad.net/maas/+bug/1783912
3

I run some tests with different setups

MAAS  Ubuntu  #Interfaces   Comment
3.3.1 22.04   1             Does not work - see above
3.1   20.04   1             No error log - but also no fabrics
2.9   20.04   1             WORKS: no errors, fabrics automatically detected
2.9   22.04   1             WORKS: no errors, fabrics automatically detected
2.9   22.04   3             WORKS: no errors, fabrics automatically detected
3.0   22.04   3             No error log - but also no fabrics

My original setup has three interfaces. I run the test with only one (basic) interface to see if there might be a problem.

Therefore my current workaround is: Use MAAS 2.9 and Ubuntu 22.04. After the installation and configuration, update to MAAS 3.3.1. Using this, the fabrics for the local interfaces are still there and it looks that everything works fine.

4

Seconding this problem. (MAAS 3.3.3) Multicast join does not work as intended with multiple interfaces and RackDs (we have 3) are not stable (services flapping constantly) - Would love this to be resolved. Stable provisioning of machines is not possible like this. We cannot just rebuild our existing provisioning infrastructure.

2023-05-22 08:45:38 twisted.internet.defer: [critical] Unhandled error in Deferred:
2023-05-22 08:45:38 twisted.internet.defer: [critical]
	Traceback (most recent call last):
	Failure: twisted.internet.error.MulticastJoinError: (b'\xe0\x00\x00v', b'\

Edit: I have added my voice to the pertaining bug mentioned above:

5

Sorry for grave-digging your Post, but this long lasting bug affects me on 3.5.0 and 3.5.1 as well.

Have You or anyone else found at least a workaround to use a Rack-Controller with a bond Interface?

provisioningserver.utils.services: [critical] Failed to update and/or record network interface configuration: Expecting value: line 1 column 1 (char 0); interfaces: {'bond0' ...