[Bug 1937075] Re: ovn-ctl: ovsdb-server startup might sometimes get stuck and not upgrade clustered database

[Brian Murray]

Hello Frode, or anyone else affected,

Accepted ovn into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/ovn/20.03.2-0ubuntu0.20.04.2 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ovn (Ubuntu Focal)
       Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-focal

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to ovn in Ubuntu.
https://bugs.launchpad.net/bugs/1937075

Title:
  ovn-ctl: ovsdb-server startup might sometimes get stuck and not
  upgrade clustered database

Status in ovn package in Ubuntu:
  Fix Released
Status in ovn source package in Focal:
  Fix Committed
Status in ovn source package in Groovy:
  Fix Released
Status in ovn source package in Hirsute:
  Fix Released
Status in ovn source package in Impish:
  Fix Released

Bug description:
  [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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1937075/+subscriptions