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.
Note, downgrading corosync and corosync-lib to the previous version fixes the issue and it starts as expected:
root@s1-san8:~ # yum downgrade corosync corosynclib
...
corosync.x86_64 0:2.3.4-7.el7_2.1 corosynclib.x86_64 0:2.3.4-7.el7_2.1
root@s1-san8:~ # systemctl start corosync
Interesting and thank you for the link, I'm sorry I didn't actually spot that myself.
We don't use PCS (yet) due to some limitations when automating cluster bootstraipping / configuration hence why we noticed it.
Again, sorry for not spotting this upstream first.
Thanks,
Sam.
(In reply to Sam McLeod from comment #4)
> Interesting and thank you for the link, I'm sorry I didn't actually spot
> that myself.
No problem, actually it's quite useful to have also BZ for anybody who hits same problem.
>
> We don't use PCS (yet) due to some limitations when automating cluster
> bootstraipping / configuration hence why we noticed it.
Yep, so for a quick workaround just follow github issue (setting cluster_name is generally recommended and it's needed for new qdevice feature). RHEL is going to get this BZ fixed with 7.3.
>
> Again, sorry for not spotting this upstream first.
I would like to thank you for high quality report.
Regards,
Honza
>
> Thanks,
> Sam.