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.

Description of problem:

If you set FENCE_JOIN=no in sysconfig/cman then the node should not wait on fencing. However if you do this, start a cluster and then reboot a node running a relocatable service, the system hangs. Error logs show it is waiting on a fencing operation.

Version-Release number of selected component (if applicable): RHEL 6


How reproducible: 100%


Steps to Reproduce:
1. Configure a cluster with FENCE_JOIN=no and a relocatable service.
2. Reboot the node where the relocatable service is running
  
Actual results:

The service never gets relocated, log files indicate waiting on a fencing operation.

Expected results:

Service relocates, cluster functions normally.

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

http://git.fedorahosted.org/git/?p=cluster.git;a=commitdiff;h=10ebf6e26eff7fd21ac245cac9876ef62ae049ca

Unit test results:

Add:

DLM_CONTROLD_OPTS="-f 0 -q 0 -r 1"

to /etc/sysconfig/cman

service cman start (doesn´t matter how many nodes)

[root@rhel6-node2 ~]# dlm_tool dump
[snip]
1337082738 set protocol 1

(for -r 1)

ps ax |grep dlm_controld
19330 ?        Ssl    0:00 dlm_controld -f 0 -q 0 -r 1

extra doc commit:

http://git.fedorahosted.org/git/?p=cluster.git;a=commitdiff;h=fda037ad25a058d0fe2a61b6972a5663276d1005

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-2013-0287.html