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):
Steps to Reproduce:
1. Specify a nodeid and 'iba' transport iin "corosync.conf'.
2. Start corosync and observe that the nodeid was ignored.
Corosync node ids are automatically generated instead of utilizing the assigned node id.
Corosync utilizes the assigned node id.
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.
Created attachment 564899 [details]
Patch from upstream git
iba: Use configured node id
Corosync was ignoring nodeid for iba transport and always used
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.
Corosync with IBA transport.
Corosync was always using autogenerated NodeID even if there were set one (in config file or by cman)
Don't ignore nodeid set by user.
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.