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

[Robie Basak]

> Verification was performed on Focal with proposed enabled

Can you confirm the package version that was used with proposed enabled
please? We've had serious regressions in the past because the version
released accidentally did not match the version tested, so I want to
make sure that the version I release is the version you tested.

Note that this is specified in the request for verification in comment
14, and I've also pointed it out in the past:
https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039745.html

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

Title:
  [SRU] Ussuri stable releases

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive ussuri series:
  Fix Committed
Status in cinder package in Ubuntu:
  Invalid
Status in designate package in Ubuntu:
  Invalid
Status in horizon package in Ubuntu:
  Invalid
Status in neutron package in Ubuntu:
  Invalid
Status in nova package in Ubuntu:
  Invalid
Status in octavia package in Ubuntu:
  Invalid
Status in cinder source package in Focal:
  Fix Committed
Status in designate source package in Focal:
  Fix Committed
Status in horizon source package in Focal:
  Fix Committed
Status in neutron source package in Focal:
  Fix Committed
Status in nova source package in Focal:
  Fix Committed
Status in octavia 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:

     * cinder 16.4.2
     * designate 10.0.2
     * horizon 18.3.5
     * neutron 16.4.2
     * nova 21.2.4
     * octavia 6.2.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/1956994/+subscriptions