Well, yes. Therefore, if unattended upgrades wants to update stuff randomly and mimic an operator, it should do it as an operator and not do it partially. I guess what I'm saying is that this is a bug in unattended upgrades, rather than pacemaker/corosync. It should have a way of defining an upgrade procedure or at least blacklist corosync and pacemaker, and many other services that require updates in specific order/way.
-- 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: upgrade from 1.1.14-2ubuntu1.8 to 1.1.14-2ubuntu1.9 breaks clusters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1903745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
