[Bug 2019755] Re: [SRU] zed stable releases

[Corey Bryant]

This bug was fixed in the package cinder - 2:21.2.0-0ubuntu1~cloud0
---------------

 cinder (2:21.2.0-0ubuntu1~cloud0) jammy-zed; urgency=medium
 .
   * New upstream release for the Ubuntu Cloud Archive.
 .
 cinder (2:21.2.0-0ubuntu1) kinetic; urgency=medium
 .
   * New stable point release for OpenStack Zed (LP: #2019755).
   * d/p/lp1945500.patch: Dropped. Fixed in stable point release.
 .
 cinder (2:21.1.0-0ubuntu2.2) kinetic-security; urgency=medium
 .
   * SECURITY REGRESSION: Regressions in other projects (LP: #2020111)
     - debian/patches/series: Do not apply CVE-2023-2088.patch until
       patches are ready for all upstream OpenStack projects.
     - CVE-2023-2088


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

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

Title:
  [SRU] zed stable releases

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive zed series:
  Fix Released
Status in cinder package in Ubuntu:
  Invalid
Status in heat package in Ubuntu:
  Invalid
Status in manila package in Ubuntu:
  Invalid
Status in nova package in Ubuntu:
  Invalid
Status in cinder source package in Kinetic:
  Fix Committed
Status in heat source package in Kinetic:
  Fix Committed
Status in manila source package in Kinetic:
  Fix Committed
Status in nova source package in Kinetic:
  Fix Committed

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:

  cinder 21.2.0
  heat 19.0.1
  manila 15.2.0
  nova 26.1.1

  [Test Case]
  The following SRU process was followed:
  https://wiki.ubuntu.com/OpenStackUpdates

  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.

  [Discussion]
  n/a

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