removing a network from a DHCP agent removes L3 rules even if it shouldn't

Bug #1851659 reported by Thomas Goirand on 2019-11-07
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description


Previously on our deployment, we had DHCP agents on the compute nodes. We decided to add network nodes, and later, move the DHCP agents from the compute nodes to the network nodes.

When removing the network from the DHCP agent, it looks like the L3 rules were also removed from the compute node, even if these were needed to access the VM which it was hosting. As a consequence, there was downtime for that instance. What I did to recover was restarting the L3 agent on that compute node, and the rules where re-added.

FYI, I was running Rocky on that deployment, with neutron 13.0.4.

This IMO is a very important thing to fix in priority.



tags: added: l3-dvr-backlog
Changed in neutron:
importance: Undecided → High
tags: added: l3-ipam-dhcp
removed: l3-dvr-backlog
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers