While I haven't been able to rule out a kernel bug yet, I do feel that there's a more general bug in error handling for neutron-dhcp-agent, in that a failure to configure DHCP in one netns should not impact others.
I have seen this general behavior of a netns-specific failure breaking dhcp globally in two cases
1. This issue, where a kernel version + MTU triggers the failure
2. https://bugs.launchpad.net/neutron/+bug/1953165 , the IPV6 address conflicts from that bug caused dhcp failures even in namespaces without conflicts.
While I haven't been able to rule out a kernel bug yet, I do feel that there's a more general bug in error handling for neutron-dhcp-agent, in that a failure to configure DHCP in one netns should not impact others.
I have seen this general behavior of a netns-specific failure breaking dhcp globally in two cases /bugs.launchpad .net/neutron/ +bug/1953165 , the IPV6 address conflicts from that bug caused dhcp failures even in namespaces without conflicts.
1. This issue, where a kernel version + MTU triggers the failure
2. https:/