Red Hat Bugzilla – Bug 819494
ip.sh assigns IP address to "wrong" interface for host with multiple interfaces on same network
Last modified: 2013-01-08 02:05:28 EST
Description of problem:
When a host has two interfaces on the same IPv4 subnet, and a RHCS managed IP is configured on the same subnet, the RHCS IP is added to the first interface returned by the "ip" tool. However, I don't want it to use this interface.
This is an issue because I have two interfaces in the same IPv4 network - one is a resilient bond which I want to use to provide the service, the other is for management access for operations staff. RHCS is choosing the non-bonded interface.
I'd like the ability to configure which interface should be used.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure host with 2 interfaces on the same IPv4 network
2. Configure RHCS on this host with IP on the same network
3. Start RHCS
RHCS IP is on the "wrong" interface.
To be able to configure RHCS to use the other interface.
Unfortunately, because of non-technical reasons, I can't place the two interfaces on different networks - so the current ip.sh behaviour is a problem for me.
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release. Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products. This request is not yet committed for inclusion in
Created attachment 597904 [details]
The parameter name has been changed from "interface" to "prefer_interface"
Created attachment 600291 [details]
Fix committed to RHEL59 cluster.git
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.