Public bug reported:
When router is going to do miration actions, the router ports device owner
changed after admin state down. But these actions will not trigger port update
event. Then ovs-agent side has wrong router port information after router admin
state up. So, l3_db should send such port_update event, or use the core plugin
do the port update work. This may realted to many upstream CI failures:
https://bugs.launchpad.net/neutron/+bug/1756301
https://bugs.launchpad.net/neutron/+bug/1717302
** 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/2089663
Title:
Router port device owner changed should send PORT resource UPDATE
event
Status in neutron:
New
Bug description:
When router is going to do miration actions, the router ports device owner
changed after admin state down. But these actions will not trigger port update
event. Then ovs-agent side has wrong router port information after router admin
state up. So, l3_db should send such port_update event, or use the core plugin
do the port update work. This may realted to many upstream CI failures:
https://bugs.launchpad.net/neutron/+bug/1756301
https://bugs.launchpad.net/neutron/+bug/1717302
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2089663/+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
