Hello Wolfgang, or anyone else affected, Accepted pacemaker into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pacemaker/1.1.14-2ubuntu1.1 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: pacemaker (Ubuntu Xenial) 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 pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1595901 Title: Missing dependency on dbus Status in pacemaker package in Ubuntu: Fix Released Status in pacemaker source package in Xenial: Fix Committed Bug description: [Impact] * Pacemaker can be disfunctional and uninstallable if dbus is not around [Test Case] * lxc launch images:ubuntu/yenial/amd64 xenial-pacemaker-bug1595901 lxc exec xenial-pacemaker-bug1595901 /bin/bash apt-get remove --purge dbus # should not be installed anyway yet # for proposed verification enable proposed before the next step apt-get install pacemaker # should pull in dbus and work [Regression Potential] * since this is not a change to source or build of the code the regression potential should be low. * if dbus is causing trouble somewhere it will now do so wherever pacemaker is installed, but as reported in the bug pacemaker just requires dbus, so there is no doubt in adding the dependency. --- The systemd unit pacemaker.service depends on dbus.service, but the package has no Dependency on the dbus package, so on a system without dbus you get: Setting up pacemaker (1.1.14-2ubuntu1) ... Installing new version of config file /etc/init.d/pacemaker ... insserv: warning: current start runlevel(s) (2 3 4 5) of script `pacemaker' overrides LSB defaults (empty). insserv: warning: current stop runlevel(s) (0 1 6) of script `pacemaker' overrides LSB defaults (empty). Failed to start pacemaker.service: Unit dbus.service not found. invoke-rc.d: initscript pacemaker, action "start" failed. dpkg: error processing package pacemaker (--configure): subprocess installed post-installation script returned error exit status 5 dpkg: dependency problems prevent configuration of pacemaker-cli-utils: pacemaker-cli-utils depends on pacemaker | pacemaker-remote; however: Package pacemaker is not configured yet. Package pacemaker-remote is not installed. Cheers Wolfgang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1595901/+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
