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:
Currently, when incorrect address is specified for local node, corosync falls back to localhost IP (127.0.0.1).

It should print error that such IP does not exist on the node and exit.

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

How reproducible:
always

Steps to Reproduce:
1. edit /etc/hosts and specify non-local IP for own host (I used 1.1.1.1)
2. service cman start 
3.
  
Actual results:
corosync[5105]:   [CPG   ] chosen downlist: sender r(0) ip(127.0.0.1) ; members(old:0 left:0)

Expected results:
Error printed that specified IP is not on local node.

Additional info:

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

Honzo, I don't think this is really a duplicate of 881694. That bug is about unplugging the cable (and in fact IP vanishing).

I was asking for error report when the IP is not there at the beginning, just to avoid (and detect and report) configuration mistakes.

Basically, from corosync point of view, it's same problem. It really doesn't matter to much if IP exists on beginning and then disappear or doesn't exist at all. Corosync will behave more or less equally incorrect.