Red Hat Bugzilla – Bug 487245
network service disabled even if NetworkManager isn't installed
Last modified: 2009-02-24 21:46:35 EST
Description of problem:
My standard kickstart file excludes NetworkManager in the %packages section (these are cluster nodes and NM really isn't needed). After doing a kickstart network install, the node reboots and comes up without networking due to the fact that the "network" service is disabled.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Kickstart, exluding NetworkManager
A system with its fingers stuck in its ears.
If anaconda sees that NetworkManager isn't installed, the network service should be enabled.
NetworkManager handles the networking by default in Fedora. If you're not using it, you need to enable the network service with a services line. This is similar to if you forcibly didn't install any other core part of Fedora
Having the installer know about defaults like this doesn't scale as you can use a single installer image with a wide variety of package repos (which may have different policies about network vs NetworkManager and similar for any other services)