[Bug 2003056] Re: [SRU] OVN 22.03.2 point release

[Alan Baghumian]

I just upgraded my whole entire Focal/Yoga cloud to use the new
versions.

A few notes:

1. The add repository command did not work, so I just manually added it:

$ sudo add-apt-repository cloud-archive:ovn-22.03-proposed
'ovn-22.03-proposed': not a valid cloud-archive name

$ echo "deb http://ubuntu-cloud.archive.canonical.com/ubuntu focal-
proposed/ovn-22.03 main" | sudo tee /etc/apt/sources.list.d/cloud-
archive-ovn.list; sudo apt-get update; sudo apt-get -y dist-upgrade

2. All my machines are fully patched and the only packages that upgraded
were the fresh OVN as well as OpenVSwitch.


3. Upgraded ovn-central units first and restart OVN services.

4. Upgraded ovn-chassis then octvia-ovn-chassis units.

5. Running floating IP ping from existing instances did not report any
interruptions.

6. Stopped and started a couple instance and tested their floating
IP(s).

7. Launched two new instances in two separate AZ(s), assigned floating
IP(s), all good!

Thank you so much for taking care of this.

Best,
Alan

-- 
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/2003056

Title:
  [SRU] OVN 22.03.2 point release

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive ovn-22.03 series:
  Fix Committed
Status in Ubuntu Cloud Archive yoga series:
  Fix Released
Status in ovn package in Ubuntu:
  Invalid
Status in ovn source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  This release sports mostly bug-fixes and we would like to make sure all of our
  supported customers have access to these improvements.
  The update contains the following package updates:

     * ovn 22.03.2

  [Test Case]

  The following SRU process was followed:

  https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates

  In order to avoid regression of existing consumers, the OpenStack team will
  run their continuous integration test against the packages that are in
  -proposed. A successful run of all available tests will be required before the
  proposed packages can be let into -updates.

  The OpenStack team will be in charge of attaching the output summary of the
  executed tests. The OpenStack team members will not mark ‘verification-done’ until
  this has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned tests are attached to this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2003056/+subscriptions