Can someone confirm that the affected systems are running systemd- networkd? That would more strongly suggest that https://bugs.launchpad.net/netplan/+bug/1815101 is related.
Based on the description and the other bug, the security update doesn't seem to have regressed pacemaker; instead, it's a preexisting pacemaker/systemd interaction that causes this problem under certain circumstances for any pacemaker update. If you believe this assessment is in error, please provide more details. I'm concerned that without resolving the systemd issue, anything we do with the pacemaker packaging in an SRU/follow-up update would simply reintroduce the condition that prompted filing this bug. -- 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
