[Bug 1960636] Re: openstack systemd services not enabled by default
Launchpad Bug Tracker
1960636 at bugs.launchpad.net
Tue Mar 15 21:31:18 UTC 2022
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 <corey.bryant at canonical.com> Wed, 02 Mar 2022 09:04:31
-0500
** Changed in: barbican (Ubuntu Impish)
Status: Fix Committed => Fix Released
--
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/1960636
Title:
openstack systemd services not enabled by default
Status in OpenStack Glance Charm:
Triaged
Status in Ubuntu Cloud Archive:
Fix Released
Status in Ubuntu Cloud Archive wallaby series:
Fix Committed
Status in Ubuntu Cloud Archive xena series:
Fix Committed
Status in aodh package in Ubuntu:
Invalid
Status in barbican package in Ubuntu:
Invalid
Status in cinder package in Ubuntu:
Invalid
Status in designate package in Ubuntu:
Invalid
Status in glance package in Ubuntu:
Invalid
Status in networking-baremetal package in Ubuntu:
Fix Released
Status in vitrage package in Ubuntu:
Invalid
Status in aodh source package in Impish:
Fix Released
Status in barbican source package in Impish:
Fix Released
Status in cinder source package in Impish:
Fix Released
Status in designate source package in Impish:
Fix Released
Status in glance source package in Impish:
Fix Released
Status in networking-baremetal source package in Impish:
Fix Released
Status in vitrage source package in Impish:
Fix Released
Bug description:
[Original Description]
I noticed that every time we have a controller reboot, the glance units (all three) return with glance-api service stopped, and the charm complains about it being stopped when it should be running.
Entering the units and manually starting those services fixes the
problem and the charm goes happy. After doing this a few times, I
noticed that those glance-api services are marked as "disabled" in
systemd, and that's why they don't come back after a reboot.
Probably the charm should set them enabled when installing?
[Description]
OpenStack packages that specify debhelper (>= 10~) or debhelper-compat (= 10) do not generate a var/lib/dpkg/info/<package>.postinst script that enables the corresponding systemd service.
For example, on impish:
sudo apt install glance-api
systemctl status glance-api will show that the service is disabled
root at i1:~# 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 Tue 2022-03-01 21:04:49 UTC; 1min 5s ago
Once fixed, it will be enabled by default.
[TestCase]
Install any service from the affected package and it will be enabled by default once fixed.
[Regression Potential]
Moving to debhelper compat level 12 changes behavior as described in the man page at https://manpages.debian.org/testing/debhelper/debhelper.7.en.html#Supported_compatibility_levels. Nothing jumps out to me as a potential regression, rather there are behavioral changes, such as what fixes this bug where the generated postinst script has different behavior. Typically I would not prefer to change the compat level in an SRU unless it fixes a high impact bug, as it does in this situation. All other openstack packages that provide systemd init scripts, and are not affected by this bug, are already at compat level 12.
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-glance/+bug/1960636/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list