[Bug 2037332] Autopkgtest regression report (cinder/2:20.3.1-0ubuntu1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted cinder (2:20.3.1-0ubuntu1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

cinder/2:20.3.1-0ubuntu1 (amd64)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#cinder

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [SRU] yoga stable releases

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive yoga series:
  Triaged
Status in aodh package in Ubuntu:
  Invalid
Status in cinder package in Ubuntu:
  Invalid
Status in glance package in Ubuntu:
  Invalid
Status in heat-dashboard package in Ubuntu:
  Invalid
Status in magnum package in Ubuntu:
  Invalid
Status in nova package in Ubuntu:
  Invalid
Status in aodh source package in Jammy:
  Triaged
Status in cinder source package in Jammy:
  Fix Committed
Status in glance source package in Jammy:
  Triaged
Status in heat-dashboard source package in Jammy:
  Triaged
Status in magnum source package in Jammy:
  Triaged
Status in nova source package in Jammy:
  Triaged

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:

  aodh 14.1.0
  cinder 20.3.1
  glance 24.2.1
  heat-dashboard 7.0.1
  magnum 14.1.1
  nova 25.2.1

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