ovn upgrades should finish with unsetting ovn-match-northd-version

Bug #2042478 reported by Edward Hope-Morley
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Charm Guide
In Progress
Peter Matulis

Bug Description

The charms will set ovn-match-northd-version=true in ovn-chassis ovsdb to support major release upgrades but it will not be unset at any point. This will mean that minor release upgrades will result in northd version mismatch errors and an ovn-controller failing to connect to the southbound db. The next release of the charms will have https://bugs.launchpad.net/charm-ovn-chassis/+bug/2030944 i.e. a new config option to make this configurable. We should add a final action to the charm-guide(s) for ovn upgrade ops to have this flag set back to false.

Revision history for this message
Alan Baghumian (alanbach) wrote :

Hi Ed,

Thank you for filing this bug.

I totally agree and we have seen this happening many times over. Different units might get the minor release updates at different times and this should not break connectivity. Automatically setting ovn-match-northd-version=false post upgrades will prevent this.


Changed in charm-guide:
importance: Undecided → High
status: New → In Progress
assignee: nobody → Peter Matulis (petermatulis)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-guide (master)
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.