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 |
Invalid
|
Undecided
|
Unassigned | ||
| manila (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
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/
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 | #1 |
| Changed in charm-manila-ganesha: | |
| status: | New → Invalid |
To post a comment you must log in.
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.