** Description changed:

  [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@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
+      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]
- TBD
+ 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.

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

Title:
  openstack systemd services not enabled by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-glance/+bug/1960636/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to