[Bug 2039176] Re: [SRU] keystone stable releases

[Launchpad Bug Tracker]

This bug was fixed in the package keystone - 2:23.0.1-0ubuntu1

---------------
keystone (2:23.0.1-0ubuntu1) lunar; urgency=medium

  * d/gbp.conf: Create stable/2023.1 branch.
  * New stable point release for OpenStack Antelope (LP: #2039176).
  * d/p/remove-dependency-on-cryptography-36.0.0.patch: Dropped. Fixed
    in stqable point release.

 -- Corey Bryant <corey.bryant at canonical.com>  Thu, 12 Oct 2023 09:00:38
-0400

** Changed in: keystone (Ubuntu Lunar)
       Status: Fix Committed => Fix Released

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

Title:
  [SRU] keystone stable releases

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive antelope series:
  Fix Committed
Status in Ubuntu Cloud Archive victoria series:
  Fix Committed
Status in Ubuntu Cloud Archive wallaby series:
  Fix Committed
Status in Ubuntu Cloud Archive xena series:
  Fix Committed
Status in Ubuntu Cloud Archive yoga series:
  Fix Committed
Status in Ubuntu Cloud Archive zed series:
  Fix Committed
Status in keystone package in Ubuntu:
  Invalid
Status in keystone source package in Jammy:
  Fix Released
Status in keystone source package in Lunar:
  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:

  keystone 23.0.1 (antelope)
  keystone 22.0.1 (zed)
  keystone 21.0.1 (yoga)
  keystone 20.0.1+snapshot (xena)
  keystone 19.0.1+snapshot (wallaby)
  keystone 18.1.0+snapshot (victoria)

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