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

[Corey Bryant]

This does not affect the yoga glance package. It seems to be limited to
wallaby and xena.

Looking at glance in xena-updates:
https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/xena-updates/+packages

It was built with debhelper 13.3.4ubuntu2~cloud0:
https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/xena-proposed/+build/22258895

There's since been a new debhelper available that includes changes to systemd postinst enabling:
https://launchpad.net/ubuntu/+source/debhelper/13.5.2ubuntu1~bpo20.04.1

So we may just need some package rebuilds. I'm going to try a new backport of glance to xena-staging to test with. glance 2:23.0.0-0ubuntu1~cloud1 will be available in xena-staging shortly at:
https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/xena-staging/+packages

** Also affects: cloud-archive
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/xena
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/wallaby
   Importance: Undecided
       Status: New

** Changed in: cloud-archive
       Status: New => Invalid

** Changed in: cloud-archive/wallaby
       Status: New => Triaged

** Changed in: cloud-archive/xena
       Status: New => Triaged

** Changed in: cloud-archive/xena
   Importance: Undecided => High

** Changed in: cloud-archive/wallaby
   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 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