Red Hat Bugzilla – Bug 51039
BOOTPROTO not being written to ifcfg-ethx at all if Protocol tab is not accessed when building interface
Last modified: 2015-03-04 20:09:25 EST
Description of Problem:
When configuring an ethernet interface through neat, there are three tabs
available to Add your configuration. One of those tabs is Protocol, where
you can set whether or not DHCP is active, etc. If this tab is not
accessed during the configuration of the interface, the BOOTPROTO setting
is not set all all in the ifcfg-ethx file, resulting in an interface that
returns OK on startup, but doesn't actually start. If you try to start it
from the command line, it exits 0 and returns nothing at all because of the
Steps to Reproduce:
1. Create an interface with neat's Add functionality, avoiding the Protocol
2. Exit neat to write the configuration
3. Note that the ifcfg-ethx file does not have a BOOTPROTO entry.
missing BOOTPROTO entry
The default in the tab is DHCP, would be okay to write that as a default.
This defect is considered MUST-FIX for Fairfax
Fixed in CVS.