Node that just rebooted is showing as "pending" to other nodes and resources are unmanageable in a RHEL 6 or 7 High Availability cluster with pacemaker

Solution Verified - Updated -

Issue

  • When the primary node is up before the second node it fences it after a certain amount of time has past. Which is expected. however, once the standby node is fenced the resources are started up by the cluster. But, when the standby node remains down and out of the cluster I can't seen to manage any of resources with the pcs commands
  • A node rebooted, starts back up, but is not configured to start pacemaker, yet the other cluster nodes show it as "pending" and can't manage any of their resources.
  • pcs commands have no effect while a node shows as "pending"

Environment

  • Red Hat Enterprise Linux (RHEL) 6 or 7 with the High Availability Add On
  • pacemaker
  • RHEL 6:
    • pacemaker is chkconfig'd off in the default runlevel
    • cman is chkconfig'd on in the default runlevel
  • RHEL 7:
    • pacemaker.service is "disabled" in systemd
    • corosync.service is "enabled" in systemd

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.