Bug 179065

Summary: ifup-aliases doesn't check ONBOOT
Product: Red Hat Enterprise Linux 4 Reporter: Jan-Patrick Perisse <perisse>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED DUPLICATE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-01-27 20:18:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Jan-Patrick Perisse 2006-01-26 22:04:53 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)

Description of problem:
When an interface is configured with ifup, the virtual interfaces attached to it (ethx:n) are also loaded despite they have ONBOOT=no configured.
This is caused by ifup-aliase NOT looking for the ONBOOT parameter.
It can be corrected by adding:
 if [ "${ONBOOT}" = "no" -o "${ONBOOT}" = "NO" ];  then
              exit 0
on the new_interface() function.

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

How reproducible:

Steps to Reproduce:
1.ifup eth0

Actual Results:  eth0 and eth0:1 are up

Expected Results:  Only eth0 should be up (eth0:1 should also be up IF is says ONBOOT=yes, otherwise ifup eth0:1 should specified to bring up the interface)

Additional info:

Comment 1 Bill Nottingham 2006-01-27 20:18:55 UTC

*** This bug has been marked as a duplicate of 155497 ***