[Bug 2009966] Re: [SRU] Magnum Stable Releases

[Felipe Reyes]

** Attachment added: "focal-wallaby - cluster template created.png"
   https://bugs.launchpad.net/ubuntu/+source/magnum/+bug/2009966/+attachment/5674706/+files/focal-wallaby%20-%20cluster%20template%20created.png

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

Title:
  [SRU] Magnum Stable Releases

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive ussuri 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 magnum package in Ubuntu:
  Invalid
Status in magnum-ui package in Ubuntu:
  Invalid
Status in magnum source package in Focal:
  Fix Committed
Status in magnum-ui source package in Focal:
  Fix Committed
Status in magnum source package in Jammy:
  Fix Released
Status in magnum-ui source package in Jammy:
  Invalid
Status in magnum source package in Kinetic:
  Fix Released
Status in magnum-ui source package in Kinetic:
  Invalid

Bug description:
  [Impact]

  The magnum project is composed of the source packages "magnum" and
  "magnum-ui", the following stable releases are available in upstream,
  but not in Ubuntu:

  OpenStack Zed / Ubuntu Kinetic
  magnum-15.0.1

  OpenStack Yoga / Ubuntu Jammy
  magnum-14.1.0

  OpenStack Xena / UCA Xena
  magnum-13.1.0

  OpenStack Wallaby / UCA Wallaby
  magnum-12.1.1
  magnum-ui-8.0.1

  OpenStack Victoria / UCA Victoria
  magnum-11.2.1
  magnum-ui-7.0.1

  OpenStack Ussuri / UCA Ussuri
  magnum-10.1.0
  magnum-ui-6.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]

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