Bug 639006

Summary:	minimal install leave broken network configuration
Product:	[Fedora] Fedora	Reporter:	Simo Sorce <ssorce>
Component:	anaconda	Assignee:	Radek Vykydal <rvykydal>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	14	CC:	fedora, jonathan, pcfe, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-05-23 16:29:47 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:
Bug Depends On:
Bug Blocks:	494832

Description Simo Sorce 2010-09-30 15:42:11 UTC

If you install f14 beta and choose the minimal install option you get a system with a broken network configuration.

NetworkManager is not (and rightly so) installed, yet ifcfg-eth0 include "NM-ConTROLLED=yes"
"network" is also not enabled by default.

upon login of course no network is available.
ifup eth0 does nothing as NM is not installed

the only way to get network is to use dhclient eth0

once that is done you can install system-config-network-tui and configure the network as you like
although it will still leave "NM-CONTROLLED=yes" in the configuration file (and NM is still not installed).



On minimal install, anaconda should properly configure ifcfg-eth0 and enable the "network" service.

Comment 1 Radek Vykydal 2010-10-06 09:22:19 UTC

This bug concerns installs where network:

- is not enabled during install
- is not configured in GUI with Connection Editor (invoked with "Configure Network" button)
- is not configured in kickstart with network command

Configuration is missing in ifcfg file in this case, so perhaps BOOTPROTO="dhcp" could be added as default configuration. (NM_CONTROLLED="yes" is harmless)

Comment 2 Simo Sorce 2010-10-06 11:48:36 UTC

Radek,
your characterization is wrong.
During install network *was* configured, and updated packages were installed from the network.
Should I revert the change of title you made ?

Comment 3 Radek Vykydal 2010-10-06 12:05:59 UTC

Ah, sorry then.
How did you configure the network? I guess it was in GUI using Connection Editor. I'd need to see some log files: 

Either these gathered before reboot (switching to tty2 with Ctrl-Alt-F2, and using scp or copy to local storage):
/tmp/anaconda.log
/tmp/syslog
/tmp/ifcfg.log

or from installed system:
/var/log/anaconda.log
/var/log/anaconda.syslog
/etc/sysconfig/network-scripts/ifcfg-eth*

Aren't you hitting this: https://bugzilla.redhat.com/show_bug.cgi?id=636526#c5 ?

Thanks

Comment 4 Simo Sorce 2010-10-06 13:04:57 UTC

(In reply to comment #3)
> Ah, sorry then.
> How did you configure the network? I guess it was in GUI using Connection
> Editor. I'd need to see some log files: 
> 
> Either these gathered before reboot (switching to tty2 with Ctrl-Alt-F2, and
> using scp or copy to local storage):
> /tmp/anaconda.log
> /tmp/syslog
> /tmp/ifcfg.log
> 
> or from installed system:
> /var/log/anaconda.log
> /var/log/anaconda.syslog
> /etc/sysconfig/network-scripts/ifcfg-eth*
> 
> Aren't you hitting this: https://bugzilla.redhat.com/show_bug.cgi?id=636526#c5
> ?

It is possible, but I forgot.
I will try to get you the requested info, but it may take a while, I will need to set up a new VM.

Comment 5 Ben Boeckel 2010-10-07 04:11:22 UTC

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

Comment 6 Ben Boeckel 2010-10-07 04:12:52 UTC

I tried recently with F14Beta and BOOTPROTO is present.

Comment 7 Radek Vykydal 2011-05-23 16:29:47 UTC


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