[Bug 2046359] Re: [SRU] bobcat stable releases

Corey Bryant 2046359 at bugs.launchpad.net
Tue Jan 16 23:07:58 UTC 2024


This bug was fixed in the package neutron - 2:23.1.0-0ubuntu1~cloud0
---------------

 neutron (2:23.1.0-0ubuntu1~cloud0) jammy-bobcat; urgency=medium
 .
   * New upstream release for the Ubuntu Cloud Archive.
 .
 neutron (2:23.1.0-0ubuntu1) mantic; urgency=medium
 .
   * d/gbp.conf: Create stable/2023.2 branch.
   * d/gbp.conf, .launchpad.yaml: Sync from cloud-archive-tools for
     bobcat.
   * New stable point release for OpenStack Bobcat (LP: #2046359).
   * d/control: Align (Build-)Depends with upstream.

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

Title:
  [SRU] bobcat stable releases

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive bobcat series:
  Fix Released
Status in designate package in Ubuntu:
  Invalid
Status in magnum package in Ubuntu:
  Invalid
Status in manila package in Ubuntu:
  Invalid
Status in neutron package in Ubuntu:
  Invalid
Status in nova package in Ubuntu:
  Invalid
Status in designate source package in Mantic:
  Fix Released
Status in magnum source package in Mantic:
  Fix Released
Status in manila source package in Mantic:
  Fix Released
Status in neutron source package in Mantic:
  Fix Released
Status in nova 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:

  designate 17.0.1
  magnum 17.0.1
  manila 17.1.0
  neutron 23.1.0
  nova 28.0.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.

  [Discussion]
  n/a

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




More information about the Ubuntu-openstack-bugs mailing list