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

[Corey Bryant]

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.

** Also affects: glance (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: glance (Ubuntu)
       Status: New => Triaged

** Changed in: glance (Ubuntu)
   Importance: Undecided => High

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