Resources do not start in a RHEL 7 High Availability cluster when starting the cluster with one or more nodes is missing

Solution Unverified - Updated -

Issue

  • If a node is down, resources do not start on node up on pcs cluster start
  • When I start one node in the cluster while the other is down for maintenance, pcs status shows that missing node as "unclean" and the node that is up won't gain quorum or manage resources.
  • If I start all nodes in the cluster except one, those nodes all show 'partition WITHOUT quorum' in pcs status and don't start managing resources.
  • My cluster resources are all Stopped when I boot a single node by itself

Environment

  • Red Hat Entreprise Linux (RHEL) 7 with the High Availability Add On
  • One or more nodes in the cluster has not started/joined the cluster
  • One of the following is present in the quorum section of /etc/corosync/corosync.conf
    • wait_for_all: 1 or
    • two_node: 1 - and wait_for_all is left unspecified.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.