Using container with 3 interfaces, errors will come in a group of 3, if there are 4 interfaces in a group of 4. I didn't notice this error when I was running MAAS inside container with 1 interface.
However I didn't notice any issues related to degradation of functionality
According to some code comments such behaviour is expected?
src/provisioningserver/utils/services.py:498
# Use the first IP address on each interface. Since the
# underlying interface is the same, joining using a
# secondary IP address on the same interface will produce
# an "Address already in use" error.
It happened to me several times last night after restarting MAAS multiple times in a row.
I was running MAAS edge inside container with 2 interfaces
8: eth0@if9: <BROADCAST, MULTICAST, UP,LOWER_ UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 3eff:fe81: 67ef/64 scope link MULTICAST, UP,LOWER_ UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 3eff:fec9: 20fd/64 scope link
link/ether 00:16:3e:81:67:ef brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 10.0.0.62/24 metric 100 brd 10.0.0.255 scope global dynamic eth0
valid_lft 2981sec preferred_lft 2981sec
inet6 fe80::216:
valid_lft forever preferred_lft forever
10: eth1@if11: <BROADCAST,
link/ether 00:16:3e:c9:20:fd brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 10.10.10.1/24 brd 10.10.10.255 scope global eth1
valid_lft forever preferred_lft forever
inet6 fe80::216:
valid_lft forever preferred_lft forever
Jul 21 15:34:50 maas maas.pebble[ 153069] : 2023-07- 21T15:34: 50.027Z [regiond] Failure: twisted. internet. error.Multicast JoinError: (b'\xe0\x00\x00v', b'\n\x00\x00>'> 153069] : 2023-07- 21T15:34: 50.027Z [regiond] Failure: twisted. internet. error.Multicast JoinError: (b'\xe0\x00\x00v', b'\n\n\n\x01',>
Jul 21 15:34:50 maas maas.pebble[
Jul 21 15:43:12 maas maas.pebble[ 154713] : 2023-07- 21T15:43: 12.017Z [rackd] Failure: twisted. internet. error.Multicast JoinError: (b'\xe0\x00\x00v', b'\n\x00\x00>', > 154713] : 2023-07- 21T15:43: 12.017Z [rackd] Failure: twisted. internet. error.Multicast JoinError: (b'\xe0\x00\x00v', b'\n\n\n\x01', 9>
Jul 21 15:43:12 maas maas.pebble[
Jul 21 15:46:31 maas maas.pebble[ 155490] : 2023-07- 21T15:46: 31.718Z [regiond] Failure: twisted. internet. error.Multicast JoinError: (b'\xe0\x00\x00v', b'\n\x00\x00>'> 155490] : 2023-07- 21T15:46: 31.718Z [regiond] Failure: twisted. internet. error.Multicast JoinError: (b'\xe0\x00\x00v', b'\n\n\n\x01',>
Jul 21 15:46:31 maas maas.pebble[
Jul 21 16:03:30 maas maas.pebble[ 157560] : 2023-07- 21T16:03: 30.877Z [regiond] Failure: twisted. internet. error.Multicast JoinError: (b'\xe0\x00\x00v', b'\n\x00\x00>'> 157560] : 2023-07- 21T16:03: 30.877Z [regiond] Failure: twisted. internet. error.Multicast JoinError: (b'\xe0\x00\x00v', b'\n\n\n\x01',>
Jul 21 16:03:30 maas maas.pebble[
Using container with 3 interfaces, errors will come in a group of 3, if there are 4 interfaces in a group of 4. I didn't notice this error when I was running MAAS inside container with 1 interface.
However I didn't notice any issues related to degradation of functionality
According to some code comments such behaviour is expected? gserver/ utils/services. py:498
src/provisionin
# Use the first IP address on each interface. Since the
# underlying interface is the same, joining using a
# secondary IP address on the same interface will produce
# an "Address already in use" error.