Red Hat Bugzilla – Full Text Bug Listing
|Summary:||drbd-rgmananger rpm package depends on Red Hat Cluster Suite version 2 but works on RHCS 3|
|Product:||Red Hat Enterprise Linux 6||Reporter:||Victor Ramirez <vramirez122000>|
|Status:||CLOSED INSUFFICIENT_DATA||QA Contact:||Cluster QE <mspqa-list>|
|Version:||6.0||CC:||agk, cluster-maint, digimer, fdinitto, lhh, mgrac, partner|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2013-04-09 15:25:58 EDT||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Victor Ramirez 2011-07-18 11:50:53 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/ # ./configure # 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 Failover works!!! 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
Comment 1 Victor Ramirez 2011-07-18 11:55:05 EDT
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.
Comment 3 digimer 2011-07-18 12:12:10 EDT
Could someone at RH or Linbit test this bug against the official DRBD RPM?
Comment 5 Fabio Massimo Di Nitto 2013-04-09 15:25:58 EDT
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.