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 743175 - Pacemaker blocks indefinitely when accessing /var/run/cluster/fenced_override
Summary: Pacemaker blocks indefinitely when accessing /var/run/cluster/fenced_override
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: pacemaker
Version: 6.2
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Andrew Beekhof
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks: 747120
TreeView+ depends on / blocked
 
Reported: 2011-10-04 04:00 UTC by Andrew Beekhof
Modified: 2012-04-03 09:57 UTC (History)
3 users (show)

Fixed In Version: pacemaker-1.1.6-2.el6
Doc Type: Technology Preview
Doc Text:
Under certain circumstances, an attempt to fence a node may have caused Pacemaker to stop responding when accessing the /var/run/cluster/fenced_override file. With this update, this error no longer occurs, and Pacemaker now works as expected in this scenario.
Clone Of:
Environment:
Last Closed: 2011-12-06 16:50:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1669 0 normal SHIPPED_LIVE pacemaker bug fix and enhancement update 2011-12-06 00:50:15 UTC

Description Andrew Beekhof 2011-10-04 04:00:35 UTC 
Description of problem:

When Pacemaker fences a node, it tries to let cman/fenced know.
However if /var/run/cluster/fenced_override is not yet open for reading, our call to open will block until it is.  This could be forever.

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

pacemaker-1.1.5-8.el6

How reproducible:
Very

Steps to Reproduce:
1.  Configure a 7 node physical cman/pacemaker cluster
2.  Run CTS with fencing enabled
3.  Watch things blow up during the initial StartOnebyOne test
  
Actual results:
The cluster logs will contain messages that "cluster nodes failed to respond to the join offer" and "Welcome reply not received from".

Attaching to any of these nodes with gdb will show them blocked in tengine_stonith_notify() trying to open /var/run/cluster/fenced_override

Expected results:

The error logic is not triggered.

Additional info:
Comment 3 Lon Hohberger 2011-10-04 23:24:56 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:
The Pacemaker Cluster Resource Manager has been rebased to version [X] from upstream.  This includes fixes from the open source community.  Pacemaker continues to be offered as a Technology Preview.
Comment 6 Andrew Beekhof 2011-10-06 05:17:23 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 @@
-The Pacemaker Cluster Resource Manager has been rebased to version [X] from upstream.  This includes fixes from the open source community.  Pacemaker continues to be offered as a Technology Preview.+The Pacemaker Cluster Resource Manager has been rebased to version 1.1.6 from upstream.  This includes fixes from the open source community.  Pacemaker continues to be offered as a Technology Preview.
Comment 9 Jaroslav Kortus 2011-10-17 15:12:43 UTC 
solved (probably) by this patch: https://github.com/ClusterLabs/pacemaker/commit/cd2d55f68642c86afe157e836811aa0239c974c1
Comment 11 Jaromir Hradilek 2011-10-26 09:31:59 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 @@
-The Pacemaker Cluster Resource Manager has been rebased to version 1.1.6 from upstream.  This includes fixes from the open source community.  Pacemaker continues to be offered as a Technology Preview.+Under certain circumstances, an attempt to fence a node may have caused Pacemaker to stop responding when accessing the /var/run/cluster/fenced_override file. With this update, this error no longer occurs, and Pacemaker now works as expected in this scenario.
Comment 16 errata-xmlrpc 2011-12-06 16:50:45 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-1669.html
Note You need to log in before you can comment on or make changes to this bug.