Public bug reported:
Hi,
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.
Cheers,
Thomas
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1851659
Title:
removing a network from a DHCP agent removes L3 rules even if it
shouldn't
Status in neutron:
New
Bug description:
Hi,
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.
Cheers,
Thomas
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1851659/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
