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 586655 [details]
Backported patch from needle

Description of problem (test case):
It's impossible to bind to concrete IP if there is previous network which is same as first one.

Version-Release number of selected component (if applicable):
Corosync in RHEL 6.3 (same in flatiron git)

How reproducible:
100%

TEST CASE:

Steps to Reproduce:
1. multiple IPs with same net

ip addrs
...
    inet 10.34.38.161/24 brd 10.34.38.255 scope global eth0
    inet 10.34.38.215/24 scope global secondary eth0
...

2. set bindnetaddr to second IP (10.34.38.215)
3. corosync
  
Actual results:

In log 

...
The network interface [10.34.38.161] is now up.
...

And corosync is really bound to 161

Expected results:

...
The network interface [10.34.38.215] is now up.
...

And corosync should be really bound to 215

    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
User has two IPs on same network and try to use second one.
 
Consequence
Corosync binds to first IP.

Fix

Logic for binding now works in following way:
- Try to find exact match
- If not exact match is found, use first found network address

Result
Use can bind to exact IP (even it is second 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