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

[Corey Bryant]

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-hyperv/debian/control: debhelper-compat (= 12),
./sahara/debian/control: debhelper-compat (= 12),
./zaqar-ui/debian/control: debhelper (>= 10),
./vmware-nsx/debian/control: debhelper-compat (= 12),
./nova/debian/control: debhelper-compat (= 12),

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