Hello, AFAICT, the same change broke creating "named" device nodes in /dev via udev, causing messages like this when running /etc/init.d/drbd reload:
# /etc/init.d/drbd reload * Reloading DRBD Configuration 1: Failure: (124) Device is attached to a disk (use detach first) Command 'drbdsetup-83 1 disk /dev/mapper/MD1-salesnet /dev/mapper/MD1-salesnet internal --set-defaults --create-device' terminated with exit code 10 Running: # udevadm test /block/drbd1 I get: ... spawn_read: '/sbin/drbdadm sh-udev minor-1'(err) 'execvp() failed to exec drbdadm-83: No such file or directory' spawn_wait: '/sbin/drbdadm sh-udev minor-1' [18952] exit with return code 20 udev_event_execute_rules: no node name set, will use kernel supplied name 'drbd1' udev_node_add: creating device node '/dev/drbd1', devnum=147:1, mode=0660, uid=0, gid=6 ... Giving me only /dev/drbd1, but no /dev/drbd_salesnet (as before) or /dev/drbd directory. Installing 2:8.4.3-0ubuntu0.12.04.2 fixed the problem. Hopefully it's related, I'm posting it up here in case somebody else gets bitten by it too. -- 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
