OVN NB db out of sync with neutron
Bug #2016552 reported by
James Page
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Juju Charmed Operator - Neutron K8S |
Triaged
|
High
|
Unassigned | ||
| OpenStack Snap |
Triaged
|
High
|
Unassigned | ||
Bug Description
OpenStack Yoga (OCI containers TBC).
After some extended period of operation with cycling of many 1000's of containers the OVN NB database had a number of ports that where not present in Neutron.
Running the OVN sync tool from the neutron container in repair mode resolved this problem but it impacted the cloud in the form of instances not being able to schedule ports through neutron.
Revision history for this message
| James Page (james-page) wrote | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Related fix proposed to charm-neutron-k8s (main) | #2 |
| Changed in charm-neutron-k8s: | |
| importance: | Undecided → High |
| Changed in snap-openstack: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| Changed in charm-neutron-k8s: | |
| status: | New → Triaged |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Related fix merged to charm-neutron-k8s (main) | #3 |
| tags: | added: in-main |
To post a comment you must log in.
I also had to tweak the ml2_conf for OVN to enable the qos extension to get the sync tool to actually work.