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 ifdown the cluster interface on a node, it somehow sees itself and another node as still members of the cluster