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

Bug 47711

Summary:	incorrect ifcfg-eth0 file: says BOOT=no despite installer check box.
Product:	[Retired] Red Hat Linux	Reporter:	Eugene Kanter <ekanter>
Component:	anaconda	Assignee:	Brent Fox <bfox>
Status:	CLOSED RAWHIDE	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-07-16 16:13:03 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:

Description Eugene Kanter 2001-07-06 16:47:16 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0)

Description of problem:
GUI install from CD, all defaults, except for manual
partitioning, workstation install. Desktop system, no PCMCIA.
Ended up with BOOT=no in ifcfg-eth0 config file.
Repeated install twice to make sure.
Changed to BOOT=yes, restarted, pump worked fine.

How reproducible:
Always

Steps to Reproduce:
Perform default GUI workstation install from CD. Choose ALL defaults 
except for manual partitioning. Partition layout is
sda1 /boot 30Meg
sda2 swap 500Meg
sda3 /    about 3.5G

4.3Gig didsk

The check box to start interface on boot is checked
by default.

Probably irrelevant, but Russan language was selected in addition to US 
English in both cases.

Actual Results:  after install eth0 is not up.

Expected Results:  after install eth0 is up.

Additional info: none.

Comment 1 Daniel Powell 2001-07-06 17:36:49 UTC

[root@localhost network-scripts]# cat ifcfg-eth0
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=no
[root@localhost network-scripts]#

Anaconda apparantly forgets to turn this to on.

Comment 2 Michael Fulbright 2001-07-10 15:30:16 UTC

What network card do you have?

Comment 3 Eugene Kanter 2001-07-10 15:48:08 UTC

network card module is 8139too

Comment 4 Brian Brock 2001-07-11 18:28:02 UTC

I've replicated this problem on two machines, with eepro100 (rev 5 and 8) and
internal tree qa0711.0.

Comment 5 Ben Levenson 2001-07-12 20:58:12 UTC

-replicated on ia64 
-qa0711.3 
-Ethernet Pro 100 rev 08

Comment 6 Glen Foster 2001-07-13 19:44:30 UTC

This defect considered MUST-FIX for Fairfax gold-release.

Comment 7 Jeremy Katz 2001-07-20 01:41:11 UTC

fixed in CVS

Comment 8 Jeremy Katz 2001-07-20 01:42:00 UTC

*** Bug 49322 has been marked as a duplicate of this bug. ***

Comment 9 Jeremy Katz 2001-07-22 16:25:28 UTC

*** Bug 49639 has been marked as a duplicate of this bug. ***