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.
@Mario: Have you filed a ticket with Red Hat support for them to triage this issue? Generally we ask that production support issues first be opened with our support organization and then they escalate to bugzilla.
Description of problem: Upgrading cluster production envinronment from RHEL6.0 to RHEL6.1 is not possible Version-Release number of selected component (if applicable): cman-3.0.12-23.el6_0.6.x86_64 clusterlib-3.0.12-23.el6_0.6.x86_64 and cman-3.0.12-41.el6.x86_64 clusterlib-3.0.12-41.el6.x86_64 Steps to Reproduce: 1. setup multinode RHEL6.0 cluster 2. shutdown one node and upgrade it to RHEL6.1 3. bring back that node to cluster Actual results: Jul 6 16:36:03 node4 corosync[2941]: [MAIN ] Corosync Cluster Engine ('1.2.3'): started and ready to provide service. Jul 6 16:36:03 node4 corosync[2941]: [MAIN ] Corosync built-in features: nss dbus rdma snmp Jul 6 16:36:03 node4 corosync[2941]: [MAIN ] Successfully read config from /etc/cluster/cluster.conf Jul 6 16:36:03 node4 corosync[2941]: [MAIN ] Successfully parsed cman config Jul 6 16:36:03 node4 corosync[2941]: [TOTEM ] Initializing transport (UDP/IP Multicast). Jul 6 16:36:03 node4 corosync[2941]: [TOTEM ] Initializing transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0). Jul 6 16:36:03 node4 corosync[2941]: [TOTEM ] The network interface [192.168.3.135] is now up. Jul 6 16:36:03 node4 corosync[2941]: [QUORUM] Using quorum provider quorum_cman Jul 6 16:36:03 node4 corosync[2941]: [SERV ] Service engine loaded: corosync cluster quorum service v0.1 Jul 6 16:36:03 node4 corosync[2941]: [CMAN ] CMAN 3.0.12 (built Mar 22 2011 05:32:49) started Jul 6 16:36:03 node4 corosync[2941]: [SERV ] Service engine loaded: corosync CMAN membership service 2.90 Jul 6 16:36:03 node4 corosync[2941]: [SERV ] Service engine loaded: openais checkpoint service B.01.01 Jul 6 16:36:03 node4 corosync[2941]: [SERV ] Service engine loaded: corosync extended virtual synchrony service Jul 6 16:36:03 node4 corosync[2941]: [SERV ] Service engine loaded: corosync configuration service Jul 6 16:36:03 node4 corosync[2941]: [SERV ] Service engine loaded: corosync cluster closed process group service v1.01 Jul 6 16:36:03 node4 corosync[2941]: [SERV ] Service engine loaded: corosync cluster config database access v1.01 Jul 6 16:36:03 node4 corosync[2941]: [SERV ] Service engine loaded: corosync profile loading service Jul 6 16:36:03 node4 corosync[2941]: [QUORUM] Using quorum provider quorum_cman Jul 6 16:36:03 node4 corosync[2941]: [SERV ] Service engine loaded: corosync cluster quorum service v0.1 Jul 6 16:36:03 node4 corosync[2941]: [MAIN ] Compatibility mode set to whitetank. Using V1 and V2 of the synchronization engine. Jul 6 16:36:03 node4 corosync[2941]: [TOTEM ] A processor joined or left the membership and a new membership was formed. Jul 6 16:36:03 node4 corosync[2941]: [QUORUM] Members[1]: 4 Jul 6 16:36:03 node4 corosync[2941]: [QUORUM] Members[1]: 4 Jul 6 16:36:03 node4 corosync[2941]: [CPG ] downlist received left_list: 0 Jul 6 16:36:03 node4 corosync[2941]: [CPG ] chosen downlist from node r(0) ip(192.168.3.135) Jul 6 16:36:03 node4 corosync[2941]: [MAIN ] Completed service synchronization, ready to provide service. *TIMEOUT* Expected results: Jul 6 16:38:47 node3 corosync[11778]: [MAIN ] Corosync Cluster Engine ('1.2.3'): started and ready to provide service. Jul 6 16:38:47 node3 corosync[11778]: [MAIN ] Corosync built-in features: nss rdma Jul 6 16:38:47 node3 corosync[11778]: [MAIN ] Successfully read config from /etc/cluster/cluster.conf Jul 6 16:38:47 node3 corosync[11778]: [MAIN ] Successfully parsed cman config Jul 6 16:38:47 node3 corosync[11778]: [TOTEM ] Initializing transport (UDP/IP). Jul 6 16:38:47 node3 corosync[11778]: [TOTEM ] Initializing transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0). Jul 6 16:38:47 node3 corosync[11778]: [TOTEM ] The network interface [192.168.3.136] is now up. Jul 6 16:38:47 node3 corosync[11778]: [QUORUM] Using quorum provider quorum_cman Jul 6 16:38:47 node3 corosync[11778]: [SERV ] Service engine loaded: corosync cluster quorum service v0.1 Jul 6 16:38:47 node3 corosync[11778]: [CMAN ] CMAN 3.0.12 (built Dec 1 2010 13:41:12) started Jul 6 16:38:47 node3 corosync[11778]: [SERV ] Service engine loaded: corosync CMAN membership service 2.90 Jul 6 16:38:47 node3 corosync[11778]: [SERV ] Service engine loaded: openais checkpoint service B.01.01 Jul 6 16:38:47 node3 corosync[11778]: [SERV ] Service engine loaded: corosync extended virtual synchrony service Jul 6 16:38:47 node3 corosync[11778]: [SERV ] Service engine loaded: corosync configuration service Jul 6 16:38:47 node3 corosync[11778]: [SERV ] Service engine loaded: corosync cluster closed process group service v1.01 Jul 6 16:38:47 node3 corosync[11778]: [SERV ] Service engine loaded: corosync cluster config database access v1.01 Jul 6 16:38:47 node3 corosync[11778]: [SERV ] Service engine loaded: corosync profile loading service Jul 6 16:38:47 node3 corosync[11778]: [QUORUM] Using quorum provider quorum_cman Jul 6 16:38:47 node3 corosync[11778]: [SERV ] Service engine loaded: corosync cluster quorum service v0.1 Jul 6 16:38:47 node3 corosync[11778]: [MAIN ] Compatibility mode set to whitetank. Using V1 and V2 of the synchronization engine. Jul 6 16:38:47 node3 corosync[11778]: [TOTEM ] A processor joined or left the membership and a new membership was formed. Jul 6 16:38:47 node3 corosync[11778]: [QUORUM] Members[1]: 3 Jul 6 16:38:47 node3 corosync[11778]: [QUORUM] Members[1]: 3 Jul 6 16:38:47 node3 corosync[11778]: [CPG ] downlist received left_list: 0 Jul 6 16:38:47 node3 corosync[11778]: [CPG ] chosen downlist from node r(0) ip(192.168.3.136) Jul 6 16:38:47 node3 corosync[11778]: [MAIN ] Completed service synchronization, ready to provide service. Jul 6 16:38:47 node3 corosync[11778]: [TOTEM ] A processor joined or left the membership and a new membership was formed. Jul 6 16:38:47 node3 corosync[11778]: [QUORUM] Members[2]: 3 5 Jul 6 16:38:47 node3 corosync[11778]: [QUORUM] Members[2]: 3 5 Jul 6 16:38:47 node3 corosync[11778]: [QUORUM] Members[3]: 2 3 5 Jul 6 16:38:47 node3 corosync[11778]: [QUORUM] Members[3]: 2 3 5 Jul 6 16:38:47 node3 corosync[11778]: [CMAN ] quorum regained, resuming activity Jul 6 16:38:47 node3 corosync[11778]: [QUORUM] This node is within the primary component and will provide service. Jul 6 16:38:47 node3 corosync[11778]: [QUORUM] Members[4]: 1 2 3 5 Jul 6 16:38:47 node3 corosync[11778]: [QUORUM] Members[4]: 1 2 3 5 Jul 6 16:38:47 node3 corosync[11778]: [QUORUM] Members[5]: 1 2 3 5 6 Jul 6 16:38:47 node3 corosync[11778]: [QUORUM] Members[5]: 1 2 3 5 6 Jul 6 16:38:47 node3 corosync[11778]: [CPG ] downlist received left_list: 0 Jul 6 16:38:47 node3 corosync[11778]: [CPG ] downlist received left_list: 0 Jul 6 16:38:47 node3 corosync[11778]: [CPG ] downlist received left_list: 0 Jul 6 16:38:47 node3 corosync[11778]: [CPG ] downlist received left_list: 0 Jul 6 16:38:47 node3 corosync[11778]: [CPG ] downlist received left_list: 0 Jul 6 16:38:47 node3 corosync[11778]: [CPG ] chosen downlist from node r(0) ip(192.168.3.138) Jul 6 16:38:47 node3 corosync[11778]: [MAIN ] Completed service synchronization, ready to provide service. *NODE UP* Additional info: