Hello Chris, or anyone else affected, Accepted pacemaker into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/pacemaker/1.1.6-2ubuntu3.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1302633 Title: pacemaker: Discarding cib_apply_diff message (<number>) from <server>: not in our membership Status in “pacemaker” package in Ubuntu: Fix Released Status in “pacemaker” source package in Precise: Fix Committed Bug description: [Impact] * Using 12.04 version of pacemaker in a VMWare enviornment will occasionally not sync on reboot. * The error message "warning: cib_peer_callback: DDiscarding cib_apply_diff message (<number>) from <server>: not in our membership" is present in log files. * It is expected the pacemaker syncs properly on reboot. [Test Case] * Run 12.04 pacemaker in a VMWare environment and reboot multiple times. * This blog post has a decent write up on what happens: http://www.tomas.cat/blog/en/troubleshooting-pacemaker-discarding-cibapplydiff-message-xxx-server2-not-our-membership [Regression Potential] * The patch https://github.com/ClusterLabs/pacemaker/commit/03f6105592281901cc10550b8ad19af4beb5f72f has been identified as solving the issue. This patch is present in pacemake-1.1.7 and beyond. This this code is in the quantal version and beyond. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1302633/+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
