Bug 626040

Summary:	Networking not activated in freshly-installed system
Product:	[Fedora] Fedora	Reporter:	Jan Engelhardt <jengelh>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	13	CC:	iarlyy, jonathan, notting, plautrba, rvokal
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-08-23 18:57:19 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 Jan Engelhardt 2010-08-21 15:45:16 UTC

Description of problem:
After a fresh installation of a system, eth0 is not set up. /etc/sysconfig/network-scripts/ifcfg-eth0 does contain the information used during anaconda installation, however, /etc/init.d/network seems to be not run on boot.

Version-Release number of selected component (if applicable):
F 13 netinst.

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 iarly selbir 2010-08-23 11:51:58 UTC

How you configured network on anaconda(dhcp,static.ipv[4,6]), and what was created on /etc/sysconfig/network-scripts/ifcfg-eth0 after system be completely installed?

Thanks for your report.

(In reply to comment #0)
> Description of problem:
> After a fresh installation of a system, eth0 is not set up.
> /etc/sysconfig/network-scripts/ifcfg-eth0 does contain the information used
> during anaconda installation, however, /etc/init.d/network seems to be not run
> on boot.
> 
> Version-Release number of selected component (if applicable):
> F 13 netinst.
> 
> How reproducible:
> 
> 
> Steps to Reproduce:
> 1.
> 2.
> 3.
> 
> Actual results:
> 
> 
> Expected results:
> 
> 
> Additional info:

Comment 2 Bill Nottingham 2010-08-23 15:54:55 UTC

Did you just do the minimal install? If you did (and therefore do not install NetworkManager), you will need to enable the network service.

Comment 3 Jan Engelhardt 2010-08-23 18:05:26 UTC

After giving the installer the network setup info, it just installs something without further questions. NetworkManager does not seem to be among that.

Comment 4 Bill Nottingham 2010-08-23 18:27:18 UTC

Was this a text mode install?

Comment 5 Jan Engelhardt 2010-08-23 18:51:50 UTC

It was indeed.

Comment 6 Bill Nottingham 2010-08-23 18:57:19 UTC

OK. text mode install is a minimal install, so it runs into the above situation.

Comment 7 Jan Engelhardt 2010-08-23 19:11:11 UTC

So what? Why can't Fedora have this fixed what other distributions already have?

Comment 8 Bill Nottingham 2010-08-23 19:40:44 UTC

The installer does not have a mechanism to enable and disable services based on the package set installed. TBH, the simplest solution would be to put NetworkManager in the minimal install.

Comment 9 Jan Engelhardt 2010-08-23 20:22:36 UTC

TBH that leaves me unsatisfied - openSUSE can do this. I think what they do is always have /etc/init.d/network in the runlevel, but let ifup (which is called as part of network) skip ethX if ifcfg-ethX has been marked as being controlled by NetworkManager.