Bug 51039 - BOOTPROTO not being written to ifcfg-ethx at all if Protocol tab is not accessed when building interface
BOOTPROTO not being written to ifcfg-ethx at all if Protocol tab is not acces...
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-network (Show other bugs)
7.3
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Phil Knirsch
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-08-06 16:30 EDT by Panic
Modified: 2015-03-04 20:09 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-08-06 18:49:13 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Panic 2001-08-06 16:30:55 EDT
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
missing entry.

How Reproducible:

Always

Steps to Reproduce:
1. Create an interface with neat's Add functionality, avoiding the Protocol
tab.
2. Exit neat to write the configuration
3. Note that the ifcfg-ethx file does not have a BOOTPROTO entry.

Actual Results:

missing BOOTPROTO entry

Expected Results:

The default in the tab is DHCP, would be okay to write that as a default.

Additional Information:
Comment 1 Glen Foster 2001-08-06 18:49:01 EDT
This defect is considered MUST-FIX for Fairfax
Comment 2 Phil Knirsch 2001-08-07 07:42:16 EDT
Fixed in CVS.

Note You need to log in before you can comment on or make changes to this bug.