Bug 684838
Summary: | After fencing of a failed node 'fenced' daemon leaves 'fenced:default' cpg on all remaining nodes | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Andrew Beekhof <abeekhof> |
Component: | pacemaker | Assignee: | Andrew Beekhof <abeekhof> |
Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
Severity: | urgent | Docs Contact: | |
Priority: | low | ||
Version: | 6.1 | CC: | abeekhof, agk, andrew, bubble, cluster-maint, djansa, fdinitto, lhh, sdake, swhiteho, teigland |
Target Milestone: | rc | Keywords: | TechPreview |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | pacemaker-1.1.5-3.el6 | Doc Type: | Technology Preview |
Doc Text: |
Previously, when pacemaker fenced a node, it would restart the fence domain while attempting to notify other nodes of the fencing event. This would put the fence domain into an incorrect state, blocking any further recovery. With this update, an upstream patch has been applied to address this issue. As a result, node recovery completes successfully.
|
Story Points: | --- |
Clone Of: | 664958 | Environment: | |
Last Closed: | 2011-05-19 13:49:42 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: | 664958 | ||
Bug Blocks: |
Description
Andrew Beekhof
2011-03-14 15:58:35 UTC
We have a fix from upstream that David has verified to be correct. Highly important that fencing works. 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: Previously, rebooting a node in a CMAN managed cluster could cause the fencing daemon to keep the "fenced:default" CPG group on the remaining nodes, leaving the cluster in an inconsistent state. With this update, an upstream patch has been applied to address this issue. As a result, when a node is rebooted and leaves a cluster, the cluster resources correctly run on remaining nodes. 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 @@ -Previously, rebooting a node in a CMAN managed cluster could cause the fencing daemon to keep the "fenced:default" CPG group on the remaining nodes, leaving the cluster in an inconsistent state. With this update, an upstream patch has been applied to address this issue. As a result, when a node is rebooted and leaves a cluster, the cluster resources correctly run on remaining nodes.+Previously, when pacemaker fenced a node, it would restart the fence domain while attempting to notify other nodes of the fencing event. This would put the fence domain into an incorrect state, blocking any further recovery. With this update, an upstream patch has been applied to address this issue. As a result, node recovery completes successfully. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0642.html |