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.

Created attachment 521159 [details]
output of corosync-fplay

Description of problem:

I'm testing a cluster setup with rhel 6.1 and I've a problem which stops me from deploying that cluster with rhel in production. Sometimes when I reboot a node with active services the corosync on the node which should to the take over crashes. It can work for some reboots and than suddenly I run into the problem. The 2 nodes are running as Vmware instances on different hosts, across 2 data centers (> 10 km distance).

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

corosync-1.2.3-36.el6.x86_64
corosynclib-1.2.3-36.el6.x86_64


How reproducible:

reboot many times and sometimes it happens.

Actual results:

crash of corosync and 100% cpu for pacemaker

Expected results:

the Cluster should swith correctly

Additional info:

see attachments

Created attachment 521165 [details]
one of the crash dumps (matches the corosync-fplay)

*** This bug has been marked as a duplicate of bug 671575 ***

Robert,

Generally I believe your deployment would need an architecture review before being processed by sales.  Also, bugs should come in from support not directly from customers.

Best wishes
-steve