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.

Description of problem:
Sometimes it happens that pcs start spawns both corosync and pacemaker, but pacemaker demands corosync connection before it is actually ready.

This leads to error messages and pacemaker not starting (which is not reported back, which is probably systemd scripts nature ;)).

The error message is this:
r7-node01 pacemakerd[3135]: Could not initialize Cluster Configuration Database API instance, error 2

Version-Release number of selected component (if applicable):


How reproducible:
sometimes

Steps to Reproduce:
1. pcs start
2. check if pacemaker is up (and no error messages are present as above)
3. 
  
Actual results:
pacemaker not starting, which is silently ignored

Expected results:
The least we can do is to implement delay between corosync start and pacemaker start, hoping for the best outcome.

Better option would be to implement checks of successful start. Maybe it's just systemd improvement that needs to be made, I'm open for suggestions :).

Additional info:

I got to the bottom of this one a few days ago.  Our retry logic was borked.

Andrew Beekhof (10 days ago) 7276f67: High: mcp: Correctly retry the connection to corosync on failure 

https://github.com/beekhof/pacemaker/commit/7276f67

I'll include this in a pacemaker build next week.


Actually, having said that, there are rare occasions when corosync simply fails to start ("service corosync start" fails and corosync is automatically stopped).

Not much pcs or pacemaker can do in that situation though.

Re-assigning to abeekhof for verification since it sounds like this was fixed a few months back in pacemaker.