Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 78992

Summary: Alias interfaces can't be disabled
Product: [Retired] Red Hat Linux Reporter: Jos Vos <jos>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED RAWHIDE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: rvokal
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-01-14 04:35:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Patch against 6.90-1 none

Description Jos Vos 2002-12-04 14:12:05 UTC 
Description of Problem:
The alias interface configuration (e.g., ifcfg-eth0:0) doesn't support a feature
to disable it.  Even if ONBOOT=no, the alias interface will be brought up
together with the parent interface.  This causes a problem in case someone wants
to control the alias interface only manually, with explicit "ifup" and "ifdown"
commands.

Version-Release number of selected component (if applicable):
All initscripts versions, up to 6.90-1.

Additional Information:
I will attach a (backwards-compatible) patch to solve this problem. If
ONPARENT=no is set in the config file, the interface will not be brought up
automatically together with the parent.
Comment 1 Bill Nottingham 2003-01-14 04:29:52 UTC 
ENOPATCH
Comment 2 Bill Nottingham 2003-01-14 04:35:52 UTC 
but something added in 7.03-1 anyway. :)
Comment 3 Jos Vos 2003-01-14 09:22:12 UTC 
Created attachment 89344 [details]
Patch against 6.90-1

Sorry, I seem to have forgotten to attach the patch earlier.  This is my patch,
don't know how this compares to your solution.
Comment 4 Bill Nottingham 2003-01-14 17:58:14 UTC 
Similar, although I note I missed the second case, which will be fixed in 7.04-1.