[Bug 2018299] Re: series-upgrade re-enables manila-share service (should be pacemaker managed)

[Alex Kavanagh]

I'm (slightly hesitatingly) re-assigning this to the manila package, as
it's the package that starts the service.  This is a debian packaging
default (to start the service on boot), but obviously it is causing
problems on series upgrade as a whole new version is being installed.
Whether we can change the package default (or inst scripts) to not
overwrite the pre-series upgrade file (or at least leave it masked if it
already is) is open to question.

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

** Changed in: charm-manila-ganesha
       Status: New => Invalid

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

Title:
  series-upgrade re-enables manila-share service (should be pacemaker
  managed)

Status in OpenStack Manila-Ganesha Charm:
  Invalid
Status in manila package in Ubuntu:
  New

Bug description:
  On a HA deployment, the manila-share service is disabled in systemd
  and managed by pacemaker.

  After series-upgrade from focal-yoga to jammy-yoga, dpkg re-enables
  the service:

  Setting up manila-share (1:14.0.1-0ubuntu1) ...
  Created symlink /etc/systemd/system/multi-user.target.wants/manila-share.service → /lib/systemd/system/manila-share.service.

  Then on each reboot, the service starts and run for 30-60 seconds
  before pacemaker runs it's monitor op and stops it again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-manila-ganesha/+bug/2018299/+subscriptions