I can confirm that drbd8-utils 2:8.4.3-0ubuntu0.12.04.2~rc4 works fine,
at least for me.
I put one node to standby, installed drbd8-utils
2:8.4.3-0ubuntu0.12.04.2~rc4, did not change drbd.conf, brought node up
again and migrated all resources to that node. Everything is working as
expected:
I can confirm that drbd8-utils 2:8.4.3-0ubuntu0.12.04.2~rc4 works fine,
at least for me.
I put one node to standby, installed drbd8-utils
2:8.4.3-0ubuntu0.12.04.2~rc4, did not change drbd.conf, brought node up
again and migrated all resources to that node. Everything is working as
expected:
I tried the fixed package in comment 60. Unfortunately, the fix did not
completely resolve the problems I had with my Corosync/Pacemaker
cluster.
I also noticed, that I had problems with the new global_common.conf parameters,
that is being installed with drbd-utils 8.4.3:
# service drbd start
*
I tried the fixed package in comment 60. Unfortunately, the fix did not
completely resolve the problems I had with my Corosync/Pacemaker
cluster.
I also noticed, that I had problems with the new global_common.conf parameters,
that is being installed with drbd-utils 8.4.3:
# service drbd start
*
I also had a problem starting DRBD with my Corosync/Pacemaker cluster
after upgrading drbd8-utils to 8.4.3.
This is a line from the log file where it is failing:
Apr 24 08:21:02 www6a lrmd: [1183]: info: RA output: (p_drbd_r0:0:start:stderr)
Could not connect to 'drbd' generic netlink family
I also had a problem starting DRBD with my Corosync/Pacemaker cluster
after upgrading drbd8-utils to 8.4.3.
This is a line from the log file where it is failing:
Apr 24 08:21:02 www6a lrmd: [1183]: info: RA output: (p_drbd_r0:0:start:stderr)
Could not connect to 'drbd' generic netlink family
