** Description changed: - As reported and fixed in [0] if the node that is configured with an - empty ``--db-*-cluster-remote-addr`` is no longer the leader, the ovn- - ctl script will hang on startup. + [Impact] + On upgrades requiring schema changes a cluster may never be upgraded, this can be problematic and might in the worst case scenario lead to data plane outage. + + Having said that it is not very likely that we will SRU changes to Focal + that includes schema changes, but it is good to be on the safe side so + we're ready for it in the event it happens. + + [Test Plan] + 1. With base in the ovn-central charm gate test we can deploy a OVN database cluster. + 2. Restart services so that DB leader transition away from the machine that created the cluster. + 3. Restart services again on original leader and confirm whether the bug is fixed. + + [Regression Potential] + The patch in question has been in upstream branches and releases for a long time, it is also a very minor change adding a argument that allows control tool to not hang when the local unit is not the leader. + + [Original Bug Description] + As reported and fixed in [0] if the node that is configured with an empty ``--db-*-cluster-remote-addr`` is no longer the leader, the ovn-ctl script will hang on startup. Prior to the hang the script will successfully start the ovsdb-server, but never get to the point where a clustered DB is upgraded in the event of a schema change. 0: https://github.com/ovn- org/ovn/commit/65cc0e225b5922a72f0d40c2c39da0210669c21a
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937075 Title: ovn-ctl: ovsdb-server startup might sometimes get stuck and not upgrade clustered database To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1937075/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
