Bug 112925 - /etc/init.d/network does not bring up slave interfaces, only bond0
/etc/init.d/network does not bring up slave interfaces, only bond0
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: initscripts (Show other bugs)
2.1
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-01-05 19:33 EST by Need Real Name
Modified: 2014-03-16 22:41 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-01-05 19:39:05 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2004-01-05 19:33:56 EST
Description of problem:

/etc/init.d/network from initscripts-6.47.6-1 does not bring up 
individual eth# interfaces (i.e. eth0, eth2, etc.), only the bond# 
(i.e bond0).  /etc/init.d/network script from initscripts-6.47.2-1.1 
and earlier works properly.

Version-Release number of selected component (if applicable): 

initscripts-6.47.6-1


How reproducible:
Every time

Steps to Reproduce:
1. setup system with 2+ NIC's and initscripts-6.47.6-1
2. setup bonding with 2 NIC's
3. /etc/init.d/network start (or restart)  
Actual results:


Expected results:


Additional info:
Comment 1 Need Real Name 2004-01-05 19:39:05 EST
Ignore.  Hit submit too early.

Note You need to log in before you can comment on or make changes to this bug.