Since the RegionD only has one address, I don't know if i can stand by my earlier assessment that this is a problem of Servers with multiple interfaces.
Another piece of information would be that all our MAAS machines are virtualized machines. Might that play into the situation with the multicast join not working correctly?
I ought to correct my assesments as i just realized, looking at the above regionD logs, that the regionD also has this multicast joining error:
2023-07-10 08:48:07 twisted. internet. defer: [critical] internet. error.Multicast JoinError: (b'\xe0\x00\x00v', b'\n\x04\x00\x0b', 98, 'Address already in use')
Traceback (most recent call last):
Failure: twisted.
Since the RegionD only has one address, I don't know if i can stand by my earlier assessment that this is a problem of Servers with multiple interfaces.
Another piece of information would be that all our MAAS machines are virtualized machines. Might that play into the situation with the multicast join not working correctly?