Bug 710696 - Setting onboot=no is no longer honored if the interface is a virtual interface
Summary: Setting onboot=no is no longer honored if the interface is a virtual interface
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts
Version: 14
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-04 05:37 UTC by John 'Warthog9' Hawley
Modified: 2014-03-17 03:27 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-06 19:09:37 UTC
Type: ---


Attachments (Terms of Use)

Description John 'Warthog9' Hawley 2011-06-04 05:37:27 UTC
Description of problem:

Setting an interface (say eth0:0) as onboot=no means that it should not come up.  Setting this on a full interface works fine.  Setting this on a virtual interface *USED* to work fine.  However it apparently stopped working at some point, and causes no end of confusion and frustration and is basically a regression from previous versions of Fedora, and an inconsistency in the configuration of ifcfg-eth interfaces.

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


How reproducible:

Always


Steps to Reproduce:
1. Define a virtual interface eth0:0 as onboot=no 
2. restart networking
3. it comes up despite this being set.
  
Actual results:

interface eth0:0 is brought up at the same time as eth0, despite eth0:0 being set onboot=no and eth0 being set onboot=yes

Expected results:

eth0 comes up eth0:0 does not.

Additional info:

Comment 1 Bill Nottingham 2011-06-06 19:09:37 UTC
From sysconfig.txt:

  Alias specific items:
    ONPARENT=yes|no
      Whether to bring up the device when the parent device is brought
      up.
      Default: yes

This isn't a recent change.


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