All HA deploys on Trusty were affected (icehouse, kilo, liberty): How to reproduce: 1) landscape-client triggers automatic apt-get upgrade corosync:amd64 (2.3.3-1ubuntu1, 2.3.3-1ubuntu2)
2) corosync restarts but pacemaker remains stopped (corosync Invalid IPC credentials) 3) on 2 deploys (icehouse and kilo), we could manually service corosync stop && service corosync start && service pacemaker start 4) on other deploys (icehouse, kilo, liberty), we had to reboot lxc <-- and always came OK It might be related to lp#1439649. -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1564250 Title: Corosync upgrade to 2.3.3-1ubuntu2 leaves pacemaker in a stopped state Status in pacemaker package in Ubuntu: Confirmed Bug description: Using pacemaker version: 1.1.10+git20130802-1ubuntu2.3 On ubuntu: Ubuntu 14.04.4 LTS Corosync upgrade to 2.3.3-1ubuntu2 leaves pacemaker in a stopped state. Specifically from version 2.3.3-1ubuntu1 I have attached logs from such upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1564250/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-ha Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
