Bug 710696

Summary:	Setting onboot=no is no longer honored if the interface is a virtual interface
Product:	[Fedora] Fedora	Reporter:	John 'Warthog9' Hawley <warthog9>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	14	CC:	iarlyy, jonathan, notting, plautrba, rvokal
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-06-06 19:09:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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.