Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #1448569 +++
Description of problem:
[root@mckinley-01 ~]# pcs status
Error: cluster is not currently running on this node
# Proposed behavior
[root@mckinley-01 ~]# pcs cluster start
Error: cluster is not currently configured on this node
# Current behavior
[root@mckinley-01 ~]# pcs cluster start
Starting Cluster...
Job for corosync.service failed because the control process exited with error code. See "systemctl status corosync.service" and "journalctl -xe" for details.
Error: unable to start corosync
[root@mckinley-01 ~]# systemctl status corosync.service
รข<97><8f> corosync.service - Corosync Cluster Engine
Loaded: loaded (/usr/lib/systemd/system/corosync.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2017-05-05 13:59:58 CDT; 30s ago
Docs: man:corosync
man:corosync.conf
man:corosync_overview
Process: 6968 ExecStart=/usr/share/corosync/corosync start (code=exited, status=1/FAILURE)
May 05 13:59:58 mckinley-01.lab.msp.redhat.com systemd[1]: Starting Corosync Cluster Engine...
May 05 13:59:58 mckinley-01.lab.msp.redhat.com corosync[6968]: Starting Corosync Cluster Engine (corosync): [FAILED]
May 05 13:59:58 mckinley-01.lab.msp.redhat.com systemd[1]: corosync.service: control process exited, code=exited status=1
May 05 13:59:58 mckinley-01.lab.msp.redhat.com systemd[1]: Failed to start Corosync Cluster Engine.
May 05 13:59:58 mckinley-01.lab.msp.redhat.com systemd[1]: Unit corosync.service entered failed state.
May 05 13:59:58 mckinley-01.lab.msp.redhat.com systemd[1]: corosync.service failed.
Version-Release number of selected component (if applicable):
pcs-0.9.157-1.el7.x86_64
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2020:1568