neutron_ovn_metadata_agent don`t work after reconnect to new OVN Southbound DB leader

Bug #1951870 reported by olmy0414
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Invalid
Undecided
Unassigned

Bug Description

**Bug Report**

What happened:
After restart of container with OVN SB_DB leader, neutron_ovn_metadata_agent reconnects to new SB_DB, according agent`s logs.
But then, during spawn of new instances, they don`t obtain metadata from nova.
Metadata agent don`t create any ovn namespaces and related ports, there are no any errors or other info in agent`s log.
As WA, this issue can be resolved by restarting of neutron_ovn_metadata_agent container.

What you expected to happen:
Correct work of neutron_ovn_metadata_agent after reconnect to new OVN Southbound DB leader

How to reproduce it (minimal and precise):
Restart container with OVN SB_DB leader and try to spawn new openstack instance.

**Environment**:
* OS: Ubuntu 20.04.3 LTS
* Kernel: 5.4.0-89-generic
* Docker version: 20.10.8
* Kolla version: 12.2.0
* Container type: ubuntu/binary
* Openstack version: wallaby

Revision history for this message
olmy0414 (oleksandr-mykhalskyi) wrote :
Revision history for this message
Michal Nasiadka (mnasiadka) wrote :

Duplicate.

Changed in kolla:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.