I'm not sure why the pacemaker task was marked as invalid. The issues
that Trent identified in comment #15 are a problem, but I'm not entirely
convinced that its *the* problem that was encountered here (as also
evidenced by Pedro in comment #16).
While packages do typically restart services automatically, not all
package upgrades will trigger this particular behavior. For example, the
ceph packages will upgrade the services but not actually restart
services as that could be very disruptive to the storage provided.
I agree with Ante in comment #9 that the packages aren't doing all of
the necessary steps to properly manage the upgrade. While, I'm not
necessarily convinced this is something that should be handled by
unattended-upgrades I'm also not convinced that it will be easy to add
this logic to the packages. For example pacemaker depends on corosync,
but so does dlm-controld and it is not reasonable for the corosync
package to make assumptions on how to treat software built on top of it.
Rather, I think it should be considered to change the behavior of the
corosync/pacemaker packages to not automatically restart the services,
or to provide an option in which the operator can control this behavior.
** Changed in: pacemaker (Ubuntu)
Status: Invalid => Confirmed
** Changed in: charm-hacluster
Assignee: (unassigned) => Billy Olsen (billy-olsen)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903745
Title:
pacemaker left stopped after unattended-upgrade of pacemaker
(1.1.14-2ubuntu1.8 -> 1.1.14-2ubuntu1.9)
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1903745/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
