Red Hat Bugzilla – Bug 722965
drbd-rgmananger rpm package depends on Red Hat Cluster Suite version 2 but works on RHCS 3
Last modified: 2013-04-09 15:25:58 EDT
Description of problem:
drbd-rgmananger rpm package depends on Red Hat Cluster Suite version 2 but works on RHCS 3. To get it working, I built the drbd package using the following commands:
# cd drbd-126.96.36.199/
# make rpm RPMOPT="--with rgmanager"
To install, I had to use the "--nodeps" option to ignore the dependency on RHCS version 2.x:
# rpm -Uvh --nodeps ~/rpmbuild/RPMS/x86_64/drbd-rgmanager-188.8.131.52-1.el6.x86_64.rpm
Unfortunately, the resource agent did not work out of the box. Perhaps I should have added a delay in the cluster.conf, but I added "sleep 1" in the beginning of the resource agent /usr/share/cluster/drbd.sh
The point is that I was tempted to use gfs2 over dual primary drbd precisely because of the drbd-rgmanager package installation obstacles and the fact that I could not find anybody else who had tried the resource agent on RHCS 3. Users should not be tempted to use dual primary drbd unless strictly necessary, since they (as I did) will struggle with frustrating split brain issues.
Version-Release number of selected component (if applicable):
- drbd 184.108.40.206 source
- RHEL 6.0 and 6.1
- Red Hat Cluster Suite 3.0.12-22.el6
P.S. I understand that is a drbd bug, not a RHCS bug. Not withstanding, I was advised to file the bug here as it would be routed to the drbd development team.
Could someone at RH or Linbit test this bug against the official DRBD RPM?
Linbit has not responded to this BZ for over 1.5 years. closing, RH does not have any way to reproduce the issue to verify where the problem is.