From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922 Description of problem: ifup script takes different paths depending on ONBOOT being set to "no" vs "NO." Changing if [ "foo$2" = "fooboot" -a "${ONBOOT}" = "no" -o "${ONBOOT}" = "NO" ] to if [ "foo$2" = "fooboot" ] && [ "${ONBOOT}" = "no" -o "${ONBOOT}" = "NO" ] seemed to resolve it. Also, commented lines in ifcfg-eth* files containing "#MASTER" cause theinterface to be brought up. This is because "MASTER=${DEVICE}" is grepped for which detects commented lines causing the interface to be brought up when ifup is called without "boot" as the second argument. Changing for device in `fgrep -l "MASTER=${DEVICE}" /etc/sysconfig/network-scripts/ifcfg-*` ; do to for device in `grep -l "^[[:space:]]*MASTER=${DEVICE}" /etc/sysconfig/network-scripts/ifcfg-*` ; do seems to resolve it. Version-Release number of selected component (if applicable): initscripts-7.31.16.EL-1 How reproducible: Always Steps to Reproduce: Configure bonding. Try ONBOOT=on or ONBOT=ON in ifcfg-ethx. Comment MASTER in ifcfg-ethx and bring up bond0. Actual Results: ONBOOT=on behaves differently than ONBOOT=ON. Commented lines in ifcfg-ethx files containing "#MASTER" cause theinterface to be brought up. Expected Results: ONBOOT=ON or on, should not be case sensative. Commenting MASTER should prevent bonding of ethx to the bond interface. Additional info:
Created attachment 105543 [details] ifup patch
*** Bug 150710 has been marked as a duplicate of this bug. ***
Fixes confirmed in initscripts-7.93.13.EL-1.
(In reply to comment #5) > Fixes confirmed in initscripts-7.93.13.EL-1. Will this fix be included in RHEL4 U1 as well as in RHEL3 U5?
It's planned, yes.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2005-117.html
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2005-123.html