Pacemaker cluster fails to start with `error: Corosync quorum is not configured`

Solution Verified - Updated -

Issue

  • Cluster fails to start after cluster restart.
  • Nodes are reported as UNCLEAN (offline)

  • Current DC shows as NONE

    # pcs status
Cluster name: my_cluster
Status of pacemakerd: 'Pacemaker is running' (last updated 2023-06-27 12:34:49 -04:00)
Cluster Summary:
* Stack: corosync
* Current DC: NONE         <----------
* Last updated: Tue Jun 27 12:34:49 2023
* Last change:  Tue Jun 27 12:29:51 2023 by root via cibadmin on rhel9a
* 2 nodes configured
* 9 resource instances configured

Node List:
* Node rhel9a: UNCLEAN (offline)      <----------
* Node rhel9b: UNCLEAN (offline)      <----------

Environment

  • Red Hat Enterprise Linux (RHEL) 7, 8 or 9 with the High Availability Add On or Resilient Storage Add On
  • Pacemaker

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content