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:
corosync ignores the cman-provided node id when using the Infiniband transport.  This prevents rgmanager from properly starting due to a failure message within DLM:

  dlm: Can't create listening comms socket
  dlm: cannot start dlm lowcomms -98  

corosync-cfgtool shows that the node ids appear to be automatically generated ids.  This prevents cman from retrieving node properties based upon the cman node id.  In the case of dlm, it is unable to query the IP addresses of the peer nodes.

Version-Release number of selected component (if applicable):
corosync-1.4.1-4.el6

How reproducible:
100%

Steps to Reproduce:
1.  Specify a nodeid and 'iba' transport iin "corosync.conf'.
2.  Start corosync and observe that the nodeid was ignored.
  
Actual results:
Corosync node ids are automatically generated instead of utilizing the assigned node id.

Expected results:
Corosync utilizes the assigned node id.

Workaround:
Configure cman's cluster.conf to utilize the same node ids as corosync generates.

Created attachment 563926 [details]
Simple patch to fix the node id assignment for Infiniband

patch looks good.  honzaf please submit upstream.

regards
-steve

Created attachment 564899 [details]
Patch from upstream git

iba: Use configured node id

Corosync was ignoring nodeid for iba transport and always used
autogenerated one.

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause
Corosync with IBA transport.

Consequence
Corosync was always using autogenerated NodeID even if there were set one (in config file or by cman)

Fix
Don't ignore nodeid set by user.

Result
Corosync now autogenerated nodeid only when user didn't entered one.

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.

http://rhn.redhat.com/errata/RHBA-2013-0497.html