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)
Steps to Reproduce:
1. multiple IPs with same net
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)
The network interface [10.34.38.161] is now up.
And corosync is really bound to 161
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.
User has two IPs on same network and try to use second one.
Corosync binds to first IP.
Logic for binding now works in following way:
- Try to find exact match
- If not exact match is found, use first found network address
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.