[Bug 1960636] Re: glance charm does not set glance-api service as enabled on boot

[Corey Bryant]

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>."

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

Title:
  glance charm does not set glance-api service as enabled on boot

Status in OpenStack Glance Charm:
  Triaged
Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive wallaby series:
  Triaged
Status in Ubuntu Cloud Archive xena series:
  Triaged
Status in glance package in Ubuntu:
  Triaged

Bug 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?

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