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

Bug #2018299 reported by Trent Lloyd
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Manila-Ganesha Charm
manila (Ubuntu)

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/ → /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.

Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

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.

Changed in charm-manila-ganesha:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.