Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 723925

Summary: [RFE] A method to disable rgmanager in cluster.conf
Product: Red Hat Enterprise Linux 6 Reporter: Lon Hohberger <lhh>
Component: rgmanagerAssignee: Lon Hohberger <lhh>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: low Docs Contact:
Priority: high    
Version: 6.2CC: cluster-maint, djansa, mjuricek
Target Milestone: rcKeywords: FutureFeature, TechPreview
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rgmanager-3.0.12.1-3.el6 Doc Type: Technology Preview
Doc Text:
As a consequence of converting the /etc/cluster.conf configuration file to be used by pacemaker, rgmanager must be disabled. The risk of not doing this is high; after a successful conversion, it would be possible to start rgmanager and pacemaker on the same host, managing the same resources. Consequently, Red Hat Enterprise Linux 6.2 includes a feature (as a Technology Preview) that forces the following requirements: rgmanager must refuse to start if it sees the <rm disabled="1"> flag in /etc/cluster.conf. rgmanager must stop any resources and exit if the <rm disabled="1"> flag appears in /etc/cluster.conf during a reconfiguration.
 Story Points: ---
Clone Of:
: 917780 (view as bug list) Environment:
Last Closed: 2011-12-06 11:59:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 917780    

Description Lon Hohberger 2011-07-21 15:00:37 UTC 
Description of problem:

As a consequence of converting cluster.conf to be used by pacemaker, it is imperative that rgmanager be disabled.  The risk of not doing this is high; it means that, after a successful conversion, it would be possible to accidentally (or intentionally) start rgmanager *and* pacemaker on the same host, managing the same resources.

Consequently, a feature is proposed which has the following requirements:

* rgmanager must refuse to start if it sees a particular flag in cluster.conf.
* rgmanager must stop any resources and exit if this particular flag appears in cluster.conf during a reconfiguration.

The proposed feature flag (in cluster.conf) is:

   <rm disabled="1" ... />

This requires a tiny update to the cluster schema as well.
Comment 4 Lon Hohberger 2011-08-01 20:28:05 UTC 
After adding 'disabled="1"' to cluster.conf, the following occurred:

node1:
Aug  1 16:23:39 snap modcluster: Updating cluster.conf
Aug  1 16:23:41 snap corosync[4620]:   [QUORUM] Members[2]: 1 2
Aug  1 16:23:41 snap rgmanager[12407]: Resource Group Manager Disabled
Aug  1 16:23:41 snap rgmanager[12407]: Shutting down
Aug  1 16:23:41 snap rgmanager[12407]: Stopping service service:1
Aug  1 16:23:41 snap rgmanager[12407]: Member 2 shutting down
Aug  1 16:23:41 snap rgmanager[12407]: Stopping service service:dang
Aug  1 16:23:41 snap rgmanager[14427]: [script] Executing /root/uhoh stop
Aug  1 16:23:42 snap rgmanager[14438]: [ip] Removing IPv4 address 192.168.122.201/24 from eth0
Aug  1 16:23:42 snap rgmanager[12407]: Service service:dang is stopped
Aug  1 16:23:52 snap rgmanager[14502]: [nfsclient] Removing export: *:/mnt/gfs2
Aug  1 16:23:53 snap rgmanager[14596]: [fs] unmounting /mnt/gfs2
Aug  1 16:23:53 snap rgmanager[12407]: Service service:1 is stopped
Aug  1 16:23:54 snap rgmanager[12407]: Disconnecting from CMAN
Aug  1 16:24:09 snap rgmanager[12407]: Exiting

node2:
Aug  1 16:23:39 crackle modcluster: Updating cluster.conf
Aug  1 16:23:40 crackle corosync[1918]:   [QUORUM] Members[2]: 1 2
Aug  1 16:23:41 crackle rgmanager[2274]: Resource Group Manager Disabled
Aug  1 16:23:41 crackle rgmanager[2274]: Shutting down
Aug  1 16:23:41 crackle rgmanager[2274]: Disconnecting from CMAN
Aug  1 16:23:41 crackle rgmanager[2274]: Exiting

When I tried to restart rgmanager:
[root@snap ~]# service rgmanager start
Starting Cluster Service Manager: rgmanager disabled in configuration; not starting
                                                           [FAILED]

[root@snap ~]# rpm -q rgmanager
rgmanager-3.0.12.1-3.el6.x86_64
Comment 5 Lon Hohberger 2011-08-01 20:37:41 UTC 
Starting rgmanager after starting cman (but before quorum was attained) had the same behavior (error while running initscript)

Starting rgmanager before starting cman netted with rgmanager dead, but no messages.  (However, this is a "don't care" case.)
Comment 6 Lon Hohberger 2011-08-01 20:38:25 UTC 
http://git.fedorahosted.org/git?p=cluster.git;a=commit;h=edc20419a06e9c96cabdf070ba676562ad22ec2c
http://git.fedorahosted.org/git?p=cluster.git;a=commit;h=8e6660824136681b73506d49776f70b8a372ec63
Comment 7 Lon Hohberger 2011-08-01 20:41:01 UTC 
https://www.redhat.com/archives/cluster-devel/2011-August/msg00004.html
https://www.redhat.com/archives/cluster-devel/2011-August/msg00005.html
Comment 11 Lon Hohberger 2011-09-28 20:49:28 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
It is now possible to disable rgmanager in cluster.conf by adding disabled="1" to the <rm> tag.  Adding this to cluster.conf will cause rgmanager to refuse to run, and any instance of rgmanager currently running will shut down services and exit.  This feature is offered as a Technology Preview to assist users wishing to run the Pacemaker Cluster Resource Manager (which is also a Technology Preview) to prevent two resource managers from running at the same time.
Comment 12 Martin Prpič 2011-11-10 13:10:48 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1,5 @@
-It is now possible to disable rgmanager in cluster.conf by adding disabled="1" to the <rm> tag.  Adding this to cluster.conf will cause rgmanager to refuse to run, and any instance of rgmanager currently running will shut down services and exit.  This feature is offered as a Technology Preview to assist users wishing to run the Pacemaker Cluster Resource Manager (which is also a Technology Preview) to prevent two resource managers from running at the same time.+As a consequence of converting the /etc/cluster.conf configuration file to be used by pacemaker, rgmanager must be disabled. The risk of not doing this is high; after a successful conversion, it would be possible to start rgmanager and pacemaker on the same host, managing the same resources.
+Consequently, Red Hat Enterprise Linux 6.2 includes a feature (as a Technology Preview) that forces the following requirements:
+
+    rgmanager must refuse to start if it sees the <rm disabled="1"> flag in /etc/cluster.conf.
+    rgmanager must stop any resources and exit if the <rm disabled="1"> flag appears in /etc/cluster.conf during a reconfiguration.
Comment 13 errata-xmlrpc 2011-12-06 11:59:51 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1595.html