openstack systemd services not enabled by default

Just spawned a new glance lxd unit using charm version 312 and ended up with glance-api service started but with it's service disabled.

ubuntu@app1maas001p:~$ juju ssh glance/3 sudo systemctl status glance-api
● glance-api.service - OpenStack Image Service API
     Loaded: loaded (/lib/systemd/system/glance-api.service; disabled; vendor preset: enabled)
     Active: active (running) since Fri 2022-02-11 15:26:53 UTC; 986ms ago
       Docs: man:glance-api(1)
   Main PID: 79156 (glance-api)
      Tasks: 1 (limit: 309316)
     Memory: 39.7M
     CGroup: /system.slice/glance-api.service
             └─79156 /usr/bin/python3 /usr/bin/glance-api --config-file=/etc/glance/glance-api.conf --log-file=/var/log/glance/glance-api.log

Feb 11 15:26:53 juju-8d8c5a-3-lxd-29 systemd[1]: Started OpenStack Image Service API.

Hi Andre and Felipe

Please could you add which version ob Ubuntu & OpenStack this is will in your respective cases. Thanks.

Alex,

Felipe is the client on the cloud I'm installing, so we both are talking about the same case.

It's ubuntu focal + openstack Xena, glance charm cs:glance-312.

Triaging as high; there is a work around, but it's awkward and this should be fixed.

Do we know why the service is getting disabled?

Tianqi has a review up at https://github.com/juju/charm-helpers/pull/676

The cause is undetermined. The bug only appears when deploying charm-glance in OpenStack bundle. Calling a function to enable the service at installation stage would be a workaround till the cause is identified.

Tianqi,

Thanks for working on this. Do you have a bundle that recreates this that you can post here?

I think we need to figure out how the service gets disabled before fixing this.

The only charm code I've found that disables systemd units is in this pause function:
https://github.com/juju/charm-helpers/blob/master/charmhelpers/core/host.py#L177

I wonder if that was called and it was not resumed? That shouldn't be called at deploy time though that I know of.

'juju run-action glance/0 pause' will run that ^ code starting here in glance:
https://opendev.org/openstack/charm-glance/src/branch/master/actions/actions.py#L43

Corey

Just FYI, I don't think 'pause' was called at any time, at least intentionally.

Hello,

The bundle I did the test on is https://github.com/openstack-charmers/openstack-bundles/tree/master/stable/openstack-base

I don't think the problem was due to a "pause" call because the service is active (just disabled). A "pause" call would stop the service. Here is the glance-api service status after deploying the above-mentioned bundle.

ubuntu@txiao-bastion:~/openstack-bundles/stable/openstack-base$ juju ssh glance/0 sudo systemctl status glance-api
● glance-api.service - OpenStack Image Service API
     Loaded: loaded (/lib/systemd/system/glance-api.service; disabled; vendor>
     Active: active (running) since Tue 2022-02-22 15:06:09 UTC; 1min 59s ago
       Docs: man:glance-api(1)
   Main PID: 32379 (glance-api)
      Tasks: 2 (limit: 2339)
     Memory: 106.0M
     CGroup: /system.slice/glance-api.service
             ├─32379 /usr/bin/python3 /usr/bin/glance-api --config-file=/etc/>
             └─32689 /usr/bin/python3 /usr/bin/glance-api --config-file=/etc/>

Feb 22 15:06:09 juju-145eb9-txiao-8 systemd[1]: Started OpenStack Image Servi>

Tianqi

This appears to be due to a packaging issue affecting the glance package (and maybe more packages).

See the screenshot comparing /var/lib/dpkg/info/glance-api.postinst from victoria (left) and wallaby (right).

Comparing the delta between the victoria and wallaby openstack-pkg-tools:

diff -Naur /home/corey/pkg/victoria/pkg/openstack-pkg-tools-113ubuntu1~cloud0/pkgos.make /home/corey/pkg/wallaby/pkg/openstack-pkg-tools-117~cloud0/pkgos.make
--- /home/corey/pkg/victoria/pkg/openstack-pkg-tools-113ubuntu1~cloud0/pkgos.make 2020-07-30 19:34:15.000000000 -0400
+++ /home/corey/pkg/wallaby/pkg/openstack-pkg-tools-117~cloud0/pkgos.make 2020-11-29 14:50:57.000000000 -0500
@@ -36,8 +36,8 @@
                fi \
        done

-override_dh_systemd_enable: gen-init-configurations
- dh_systemd_enable
+override_dh_installsystemd: gen-init-configurations
+ dh_installsystemd

 override_dh_installinit: gen-init-configurations
        dh_installinit --error-handler=true

The dh_installsystemd man page seems to infer that services are enabled by default, so it is unclear to me why the generated postinst scripts don't do that.

This does not affect the yoga glance package. It seems to be limited to wallaby and xena.

Looking at glance in xena-updates:
https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/xena-updates/+packages

It was built with debhelper 13.3.4ubuntu2~cloud0:
https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/xena-proposed/+build/22258895

There's since been a new debhelper available that includes changes to systemd postinst enabling:
https://launchpad.net/ubuntu/+source/debhelper/13.5.2ubuntu1~bpo20.04.1

So we may just need some package rebuilds. I'm going to try a new backport of glance to xena-staging to test with. glance 2:23.0.0-0ubuntu1~cloud1 will be available in xena-staging shortly at:
https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/xena-staging/+packages

UPDATE: That won't work, backports isn't enabled for builds.

This affects impish as well.

This appears to be a problem that goes away with debhelper-compat (= 12). The following are openstack packages that provide systemd init scripts, and the output is from the stable/xena branches. I've tested installing various binary packges from these and everything so far that has debhelper-compat (= 12) has it's systemd init script enabled, and everything so far that has debhelper (>= 10~) or debhelper-compat (= 10) has it's systemd init script disabled.

$ find . -name control | xargs grep debhelper
./networking-l2gw/debian/control: debhelper-compat (= 12),
./horizon/debian/control: debhelper-compat (= 12),
./designate-dashboard/debian/control: debhelper-compat (= 12),
./sahara-dashboard/debian/control: debhelper-compat (= 12),
./aodh/debian/control: debhelper (>= 10~),
./openstack-trove/debian/control: debhelper-compat (= 12),
./vitrage/debian/control: debhelper-compat (= 10),
./heat-dashboard/debian/control: debhelper-compat (= 12),
./swift/debian/control: debhelper-compat (= 12),
./masakari/debian/control: debhelper-compat (= 12),
./sahara-plugin-vanilla/debian/control: debhelper-compat (= 12),
./watcher-dashboard/debian/control: debhelper-compat (= 12),
./murano-dashboard/debian/control: debhelper-compat (= 12),
./ovn-octavia-provider/debian/control: debhelper-compat (= 12),
./masakari-monitors/debian/control: debhelper-compat (= 12),
./designate/debian/control: debhelper (>= 10~),
./murano-agent/debian/control: debhelper-compat (= 12),
./barbican/debian/control: debhelper (>= 10~),
./networking-odl/debian/control: debhelper-compat (= 12),
./neutron/debian/control: debhelper-compat (= 12),
./ceilometer/debian/control: debhelper-compat (= 12),
./placement/debian/control: debhelper-compat (= 12),
./networking-bagpipe/debian/control: debhelper-compat (= 12),
./heat/debian/control: debhelper-compat (= 12),
./networking-sfc/debian/control: debhelper-compat (= 12),
./senlin/debian/control: debhelper-compat (= 12),
./ironic-inspector/debian/control: debhelper-compat (= 12),
./octavia/debian/control: debhelper-compat (= 12),
./keystone/debian/control: debhelper-compat (= 12),
./gnocchi/debian/control: debhelper-compat (= 12),
./octavia-dashboard/debian/control: debhelper-compat (= 12),
./ironic/debian/control: debhelper-compat (= 12),
./networking-baremetal/debian/control: debhelper-compat (= 10),
./cinder/debian/control: debhelper (>= 10~),
./magnum-ui/debian/control: debhelper-compat (= 12),
./murano/debian/control: debhelper-compat (= 12),
./ironic-ui/debian/control: debhelper (>= 10~),
./watcher/debian/control: debhelper-compat (= 12),
./mistral/debian/control: debhelper-compat (= 12),
./magnum/debian/control: debhelper-compat (= 12),
./neutron-vpnaas/debian/control: debhelper-compat (= 12),
./manila-ui/debian/control: debhelper-compat (= 12),
./trove-dashboard/debian/control: debhelper-compat (= 12),
./neutron-dynamic-routing/debian/control: debhelper-compat (= 12),
./glance/debian/control: debhelper (>= 10~),
./networking-bgpvpn/debian/control: debhelper-compat (= 12),
./zaqar/debian/control: debhelper-compat (= 12),
./manila/debian/control: debhelper-compat (= 12),
./neutron-fwaas/debian/control: debhelper-compat (= 12),
./networking-hy...

It's hard for me to tell what compat level a package build used in launchpad, but the man page for debhelper [1] discourages compat level 11:

https://manpages.debian.org/testing/debhelper/debhelper.7.en.html

"This mode is discouraged.

The compat 11 is discouraged for new packages as it suffers from feature interaction between dh_installinit and dh_installsystemd causing services to not run correctly in some cases. Please consider using compatibility mode 10 or 12 instead. More details about the issue are available in Debian#887904 and <https://lists.debian.org/debian-release/2019/04/msg01442.html>."

Affected jammy/yoga packages:
./networking-baremetal/debian/control: debhelper-compat (= 10),

Affected impish/xena packages:
./aodh/debian/control: debhelper (>= 10~),
./vitrage/debian/control: debhelper-compat (= 10),
./designate/debian/control: debhelper (>= 10~),
./barbican/debian/control: debhelper (>= 10~),
./networking-baremetal/debian/control: debhelper-compat (= 10),
./cinder/debian/control: debhelper (>= 10~),
./ironic-ui/debian/control: debhelper (>= 10~), # correction: not affected, does not provide init script
./glance/debian/control: debhelper (>= 10~),
./zaqar-ui/debian/control: debhelper (>= 10), # correction: not affected, does not provide init script

Affected wallaby packages:
./aodh/debian/control: debhelper (>= 10~),
./vitrage/debian/control: debhelper-compat (= 10),
./designate/debian/control: debhelper (>= 10~),
./barbican/debian/control: debhelper (>= 10~),
./networking-baremetal/debian/control: debhelper-compat (= 10),
./cinder/debian/control: debhelper (>= 10~),
./ironic-ui/debian/control: debhelper (>= 10~), # correction: not affected, does not provide init script
./glance/debian/control: debhelper (>= 10~),
./zaqar-ui/debian/control: debhelper (>= 10), # correction: not affected, does not provide init script

This bug was fixed in the package networking-baremetal - 5.1.0+git2022030210.33aa103-0ubuntu1~cloud0
---------------

 networking-baremetal (5.1.0+git2022030210.33aa103-0ubuntu1~cloud0) focal-yoga; urgency=medium
 .
   * New upstream release for the Ubuntu Cloud Archive.
 .
 networking-baremetal (5.1.0+git2022030210.33aa103-0ubuntu1) jammy; urgency=medium
 .
   * d/control, d/rules: Switch to debhelper compat 13 and pybuild (LP: #1960636).
   * New upstream snapshot for OpenStack Yoga.
   * d/control: Align (Build-)Depends with upstream.
   * d/p/skip-test-agent-type.patch: Skip until fixed upstream.

Hello Andre, or anyone else affected,

Accepted vitrage into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/vitrage/7.5.0-0ubuntu2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-impish. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Andre, or anyone else affected,

Accepted networking-baremetal into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/networking-baremetal/5.0.0-0ubuntu2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-impish. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Andre, or anyone else affected,

Accepted glance into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glance/2:23.0.0-0ubuntu2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-impish. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Andre, or anyone else affected,

Accepted aodh into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/aodh/1:13.0.0-0ubuntu2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-impish. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Andre, or anyone else affected,

Accepted barbican into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/barbican/2:13.0.0-0ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-impish. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Andre, or anyone else affected,

Accepted cinder into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cinder/2:19.0.0-0ubuntu3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-impish. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Andre, or anyone else affected,

Accepted designate into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/designate/1:13.0.0-0ubuntu2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-impish. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Andre, or anyone else affected,

Accepted aodh into wallaby-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:wallaby-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-wallaby-needed to verification-wallaby-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-wallaby-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Andre, or anyone else affected,

Accepted barbican into wallaby-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:wallaby-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-wallaby-needed to verification-wallaby-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-wallaby-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Andre, or anyone else affected,

Accepted cinder into wallaby-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:wallaby-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-wallaby-needed to verification-wallaby-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-wallaby-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Andre, or anyone else affected,

Accepted designate into wallaby-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:wallaby-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-wallaby-needed to verification-wallaby-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-wallaby-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Andre, or anyone else affected,

Accepted glance into wallaby-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:wallaby-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-wallaby-needed to verification-wallaby-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-wallaby-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Andre, or anyone else affected,

Accepted networking-baremetal into wallaby-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:wallaby-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-wallaby-needed to verification-wallaby-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-wallaby-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Andre, or anyone else affected,

Accepted vitrage into wallaby-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:wallaby-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-wallaby-needed to verification-wallaby-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-wallaby-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Andre, or anyone else affected,

Accepted aodh into xena-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:xena-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-xena-needed to verification-xena-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-xena-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Andre, or anyone else affected,

Accepted barbican into xena-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:xena-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-xena-needed to verification-xena-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-xena-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Andre, or anyone else affected,

Accepted cinder into xena-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:xena-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-xena-needed to verification-xena-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-xena-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Andre, or anyone else affected,

Accepted designate into xena-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:xena-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-xena-needed to verification-xena-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-xena-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Andre, or anyone else affected,

Accepted glance into xena-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:xena-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-xena-needed to verification-xena-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-xena-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Andre, or anyone else affected,

Accepted networking-baremetal into xena-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:xena-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-xena-needed to verification-xena-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-xena-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Andre, or anyone else affected,

Accepted vitrage into xena-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:xena-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-xena-needed to verification-xena-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-xena-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

This bug was fixed in the package networking-baremetal - 5.1.0+git2022030210.33aa103-0ubuntu1

---------------
networking-baremetal (5.1.0+git2022030210.33aa103-0ubuntu1) jammy; urgency=medium

  * d/control, d/rules: Switch to debhelper compat 13 and pybuild (LP: #1960636).
  * New upstream snapshot for OpenStack Yoga.
  * d/control: Align (Build-)Depends with upstream.
  * d/p/skip-test-agent-type.patch: Skip until fixed upstream.

 -- Corey Bryant <email address hidden> Wed, 02 Mar 2022 10:42:51 -0500

Verified successfully on all affected releases, please see attached.

The verification of the Stable Release Update for glance has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package glance - 2:23.0.0-0ubuntu2

---------------
glance (2:23.0.0-0ubuntu2) impish; urgency=medium

  * d/gbp.conf: Create stable/xena branch.
  * d/control, d/rules: Bump debhelper compat to 12 (LP: #1960636).

 -- Corey Bryant <email address hidden> Tue, 01 Mar 2022 14:58:52 -0500

This bug was fixed in the package vitrage - 7.5.0-0ubuntu2

---------------
vitrage (7.5.0-0ubuntu2) impish; urgency=medium

  * d/gbp.conf: Create stable/xena branch.
  * d/control, d/rules: Bump debhelper compat to 12 (LP: #1960636).

 -- Corey Bryant <email address hidden> Wed, 02 Mar 2022 10:44:32 -0500

This bug was fixed in the package networking-baremetal - 5.0.0-0ubuntu2

---------------
networking-baremetal (5.0.0-0ubuntu2) impish; urgency=medium

  * d/gbp.conf: Create stable/xena branch.
  * d/control, d/rules: Bump debhelper compat to 12 (LP: #1960636).

 -- Corey Bryant <email address hidden> Wed, 02 Mar 2022 12:06:55 -0500

This bug was fixed in the package aodh - 1:13.0.0-0ubuntu2

---------------
aodh (1:13.0.0-0ubuntu2) impish; urgency=medium

  * d/gbp.conf: Create stable/xena branch.
  * d/control, d/rules: Bump debhelper compat to 12 (LP: #1960636).

 -- Corey Bryant <email address hidden> Wed, 02 Mar 2022 09:04:31 -0500

This bug was fixed in the package barbican - 2:13.0.0-0ubuntu1.1

---------------
barbican (2:13.0.0-0ubuntu1.1) impish; urgency=medium

  * d/gbp.conf: Create stable/xena branch.
  * d/control, d/rules: Bump debhelper compat to 12 (LP: #1960636).

 -- Corey Bryant <email address hidden> Wed, 02 Mar 2022 09:09:54 -0500

This bug was fixed in the package cinder - 2:19.0.0-0ubuntu3

---------------
cinder (2:19.0.0-0ubuntu3) impish; urgency=medium

  * d/gbp.conf: Create stable/xena branch.
  * d/control, d/rules: Bump debhelper compat to 12 (LP: #1960636).

 -- Corey Bryant <email address hidden> Wed, 02 Mar 2022 09:18:12 -0500

This bug was fixed in the package designate - 1:13.0.0-0ubuntu2

---------------
designate (1:13.0.0-0ubuntu2) impish; urgency=medium

  * d/gbp.conf: Create stable/xena branch.
  * d/control, d/rules: Bump debhelper compat to 12 (LP: #1960636).

 -- Corey Bryant <email address hidden> Wed, 02 Mar 2022 09:29:56 -0500

The verification of the Stable Release Update for aodh has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package aodh - 1:13.0.0-0ubuntu2~cloud0
---------------

 aodh (1:13.0.0-0ubuntu2~cloud0) focal-xena; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 aodh (1:13.0.0-0ubuntu2) impish; urgency=medium
 .
   * d/gbp.conf: Create stable/xena branch.
   * d/control, d/rules: Bump debhelper compat to 12 (LP: #1960636).

The verification of the Stable Release Update for barbican has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package barbican - 2:13.0.0-0ubuntu1.1~cloud0
---------------

 barbican (2:13.0.0-0ubuntu1.1~cloud0) focal-xena; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 barbican (2:13.0.0-0ubuntu1.1) impish; urgency=medium
 .
   * d/gbp.conf: Create stable/xena branch.
   * d/control, d/rules: Bump debhelper compat to 12 (LP: #1960636).

The verification of the Stable Release Update for aodh has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package aodh - 1:12.0.0-0ubuntu1~cloud1
---------------

 aodh (1:12.0.0-0ubuntu1~cloud1) focal-wallaby; urgency=medium
 .
   * d/gbp.conf: Create stable/wallaby branch.
   * d/control, d/rules: Bump debhelper compat to 12 (LP: #1960636).

The verification of the Stable Release Update for cinder has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package cinder - 2:19.0.0-0ubuntu3~cloud0
---------------

 cinder (2:19.0.0-0ubuntu3~cloud0) focal-xena; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 cinder (2:19.0.0-0ubuntu3) impish; urgency=medium
 .
   * d/gbp.conf: Create stable/xena branch.
   * d/control, d/rules: Bump debhelper compat to 12 (LP: #1960636).

The verification of the Stable Release Update for barbican has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package barbican - 2:12.0.0-0ubuntu2~cloud1
---------------

 barbican (2:12.0.0-0ubuntu2~cloud1) focal-wallaby; urgency=medium
 .
   * d/control, d/rules: Bump debhelper compat to 12 (LP: #1960636).

The verification of the Stable Release Update for designate has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package designate - 1:13.0.0-0ubuntu2~cloud0
---------------

 designate (1:13.0.0-0ubuntu2~cloud0) focal-xena; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 designate (1:13.0.0-0ubuntu2) impish; urgency=medium
 .
   * d/gbp.conf: Create stable/xena branch.
   * d/control, d/rules: Bump debhelper compat to 12 (LP: #1960636).

The verification of the Stable Release Update for glance has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package glance - 2:23.0.0-0ubuntu2~cloud0
---------------

 glance (2:23.0.0-0ubuntu2~cloud0) focal-xena; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 glance (2:23.0.0-0ubuntu2) impish; urgency=medium
 .
   * d/gbp.conf: Create stable/xena branch.
   * d/control, d/rules: Bump debhelper compat to 12 (LP: #1960636).

The verification of the Stable Release Update for cinder has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package cinder - 2:18.1.0-0ubuntu1~cloud1
---------------

 cinder (2:18.1.0-0ubuntu1~cloud1) focal-wallaby; urgency=medium
 .
   * d/control, d/rules: Bump debhelper compat to 12 (LP: #1960636).

The verification of the Stable Release Update for designate has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package designate - 1:12.0.1-0ubuntu1~cloud1
---------------

 designate (1:12.0.1-0ubuntu1~cloud1) focal-wallaby; urgency=medium
 .
   * d/control, d/rules: Bump debhelper compat to 12 (LP: #1960636).

The verification of the Stable Release Update for networking-baremetal has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package networking-baremetal - 5.0.0-0ubuntu2~cloud0
---------------

 networking-baremetal (5.0.0-0ubuntu2~cloud0) focal-xena; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 networking-baremetal (5.0.0-0ubuntu2) impish; urgency=medium
 .
   * d/gbp.conf: Create stable/xena branch.
   * d/control, d/rules: Bump debhelper compat to 12 (LP: #1960636).

The verification of the Stable Release Update for glance has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package glance - 2:22.1.0-0ubuntu1~cloud1
---------------

 glance (2:22.1.0-0ubuntu1~cloud1) focal-wallaby; urgency=medium
 .
   * d/control, d/rules: Bump debhelper compat to 12 (LP: #1960636).

The verification of the Stable Release Update for vitrage has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package vitrage - 7.5.0-0ubuntu2~cloud0
---------------

 vitrage (7.5.0-0ubuntu2~cloud0) focal-xena; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 vitrage (7.5.0-0ubuntu2) impish; urgency=medium
 .
   * d/gbp.conf: Create stable/xena branch.
   * d/control, d/rules: Bump debhelper compat to 12 (LP: #1960636).

The verification of the Stable Release Update for networking-baremetal has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package networking-baremetal - 4.0.0-0ubuntu1~cloud1
---------------

 networking-baremetal (4.0.0-0ubuntu1~cloud1) focal-wallaby; urgency=medium
 .
   * d/gbp.conf: Create stable/wallaby branch.
   * d/control, d/rules: Bump debhelper compat to 12 (LP: #1960636).

The verification of the Stable Release Update for vitrage has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package vitrage - 7.4.0-0ubuntu2~cloud0
---------------

 vitrage (7.4.0-0ubuntu2~cloud0) focal-wallaby; urgency=medium
 .
   * d/gbp.conf: Create stable/wallaby branch.
   * d/control, d/rules: Bump debhelper compat to 12 (LP: #1960636).
 .
 vitrage (7.4.0-0ubuntu1) hirsute; urgency=medium
 .
   * d/watch: Scope to 7.x series and update URL.
   * New upstream release for OpenStack Wallaby.