Bug 722965

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>
Component:	resource-agents	Assignee:	LINBIT <partner>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Cluster QE <mspqa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0	CC:	agk, cluster-maint, fdinitto, lhh, mgrac, mkelly, partner
Target Milestone:	rc	Keywords:	Tracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-04-09 19:25:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Victor Ramirez 2011-07-18 15:50:53 UTC

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-8.3.8.1/
# ./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-8.3.8.1-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 8.3.8.1 source
 - RHEL 6.0 and 6.1
 - Red Hat Cluster Suite 3.0.12-22.el6

Comment 1 Victor Ramirez 2011-07-18 15:55:05 UTC

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 Madison Kelly 2011-07-18 16:12:10 UTC

Could someone at RH or Linbit test this bug against the official DRBD RPM?

Comment 5 Fabio Massimo Di Nitto 2013-04-09 19:25:58 UTC

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.