[Bug 2039906] Re: [SRU] openvswitch 3.2.1 point release

James Page 2039906 at bugs.launchpad.net
Thu Feb 1 08:41:12 UTC 2024


This bug was fixed in the package openvswitch - 3.2.1-0ubuntu0.23.10.1~cloud0
---------------

 openvswitch (3.2.1-0ubuntu0.23.10.1~cloud0) jammy-bobcat; urgency=medium
 .
   * New upstream release for the Ubuntu Cloud Archive.
 .
 openvswitch (3.2.1-0ubuntu0.23.10.1) mantic; urgency=medium
 .
   * New upstream point release (LP: #2039906).
   * d/p/docs-*: Drop, included in point release.
   * d/p/lib-fatal-signal-Drop-logging-of-failed-dummy-backtr.patch: Drop,
     included in point release.
   * d/p/tests*.patch: Cherry-pick in-flight patches for tests that fixes
     autopkgtest failures.
   * d/t/*-skip-tests.txt: Add flaky test to list.


** Changed in: cloud-archive/bobcat
       Status: Fix Committed => Fix Released

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

Title:
  [SRU] openvswitch 3.2.1 point release

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive bobcat series:
  Fix Released
Status in openvswitch package in Ubuntu:
  New
Status in openvswitch source package in Mantic:
  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:

     * openvswitch 3.2.1

  [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/2039906/+subscriptions




More information about the Ubuntu-openstack-bugs mailing list