[Bug 1943712] Re: [SRU] Ussuri stable releases

[Chris MacNaughton]

** Changed in: swift (Ubuntu)
       Status: Fix Released => Invalid

** Changed in: placement (Ubuntu)
       Status: Fix Released => Invalid

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

** Changed in: neutron (Ubuntu)
       Status: Fix Released => Invalid

** Changed in: barbican (Ubuntu)
       Status: Fix Released => Invalid

** Changed in: heat (Ubuntu)
       Status: Fix Released => Invalid

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

Title:
   [SRU] Ussuri stable releases

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive ussuri series:
  New
Status in barbican package in Ubuntu:
  Invalid
Status in heat package in Ubuntu:
  Invalid
Status in keystone package in Ubuntu:
  Invalid
Status in neutron package in Ubuntu:
  Invalid
Status in placement package in Ubuntu:
  Invalid
Status in swift package in Ubuntu:
  Invalid
Status in barbican source package in Focal:
  Fix Committed
Status in heat source package in Focal:
  Fix Committed
Status in keystone source package in Focal:
  Fix Committed
Status in neutron source package in Focal:
  New
Status in placement source package in Focal:
  Fix Committed
Status in swift source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  This release sports mostly bug-fixes and we would like to make sure all of our
  users have access to these improvements.

  The update contains the following package updates:

     * barbican 10.1.0
     * heat 14.2.0
     * keystone 17.0.1
     * neutron 16.4.1
     * placement 3.0.1
     * swift 2.25.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.

  [Discussion]

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