@adam-collard hello ! Thanks for progressing this issue.
I believe stopping MAAS isn't a good way to verify that this issue is fixed, see comments 7 to 9 as to why. Basically, we experience this bug in two different scenarios :
a) packets to the MAAS servers are iptables-DROPed. Adding a REJECT rules works around the problem.
b) MAAS accepts the TCP connection, but does nothing with it (because it's spinning on CPU for some reason). Restarting (or stopping) MAAS works around the problem.
@adam-collard hello ! Thanks for progressing this issue.
I believe stopping MAAS isn't a good way to verify that this issue is fixed, see comments 7 to 9 as to why. Basically, we experience this bug in two different scenarios :
a) packets to the MAAS servers are iptables-DROPed. Adding a REJECT rules works around the problem.
b) MAAS accepts the TCP connection, but does nothing with it (because it's spinning on CPU for some reason). Restarting (or stopping) MAAS works around the problem.