Hello Stefan, or anyone else affected, Accepted drbd8 into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/drbd8/2:8.4.3-0ubuntu0.12.04.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! ** Changed in: drbd8 (Ubuntu Precise) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/1314289 Title: [Precise/regression] drbd 8.4.x backport breaks existing clusters Status in “drbd8” package in Ubuntu: Triaged Status in “drbd8” source package in Precise: Fix Committed Bug description: SRU Justification: The backport of drbd8-utils-8.4.3 has several issues when running in compat-8.3 mode as part of corosync/pacemaker clusters. Impact: - The OCF resource agent fails to run after installing the new toolset - "syncer command not supported" messages - the OCF resource agent script uses the new syntax hard coded in one place - the drbdsetup command is not using the compat binary for help output and the command line changed significantly. - if the main commands are called with the full path, the compat binaries are searched in the same path but only existed in /lib/drbd. Apart from those serious problems, the init.d script would fail in compat mode due to syntax changes. Testcases: - With new tools, old kernel module loaded: * "drbdsetup xml net" should output xml help instead of an error * "/sbin/drbdadm --version" does not fail to print the version. * "service drbd stop" should work without errors * "service corosync restart" on a cluster should work without loosing the local mirror. - Moving one side of the cluster to a newer kernel (new kernel module) * "drbdsetup xml net" should now error and need the new format. regression from bug 1185756. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1314289/+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
