One node that is expected to be without quorum fences multiple others when testing failure scenarios with ifdown in a RHEL 6 High Availability cluster
Issue
- We are testing cluster failures with
ifdown, and expect to see the failed node fenced, but instead it fences the other nodes despite it not having quorum - The node without quorum apparently fenced the other 2 nodes after taking its network interface down with
ifdown. - When we
ifdownthe cluster interface on a node, it somehow sees itself and another node as still members of the cluster
Environment
- Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
- A cluster of three or more nodes
- Using
ifdownto simulate network failures
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
