Bug 1475127 - Specify the requirement of stonith/fencing configuration for supported cluster
Specify the requirement of stonith/fencing configuration for supported cluster
Status: NEW
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation (Show other bugs)
10.0 (Newton)
All Linux
unspecified Severity medium
: ---
: ---
Assigned To: RHOS Documentation Team
RHOS Documentation Team
Depends On:
  Show dependency treegraph
Reported: 2017-07-26 02:39 EDT by Jaison Raju
Modified: 2018-07-06 10:11 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jaison Raju 2017-07-26 02:39:30 EDT
For a supported pacemaker cluster stonith is expected to be configured so that auto recovery is possible .
Many a times customer does not opt this as there is no reference of this in RHOS docs .
Some times customer dont configure as they dont want so much sofistication or dont have highly reliable network or a fence device for such configuration .
Nevertheless auto recover feature is expected for a Red Hat supported cluster .

>> This information needs to be added in following doc:

Here is some information that needs to be added :

You must configure a fencing device for each node in the cluster. For general information about configuring fencing devices, see the Red Hat Enterprise Linux 7 High Availability Add-On Reference.

Fencing Requirements
For RHEL 6 and RHEL 7 High Availability Clusters with pacemaker, you must have the cluster property stonith-enabled set to true. Even with devices configured, if stonith-enabled is false, these devices will not be used and the configuration is functionally equivalent to not having any fence devices at all.

Auto recovery cannot be expected without stonith configuration .
This bug should be cloned for all versions RHOS7-RHOS11 & future .

Note You need to log in before you can comment on or make changes to this bug.