Bug 810655 - anaconda creates NetworkManager controlled interfaces although NM isn't installed
Summary: anaconda creates NetworkManager controlled interfaces although NM isn't insta...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 16
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-07 19:14 UTC by Frantisek Hanzlik
Modified: 2012-04-08 02:10 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-08 01:27:38 UTC
Type: Bug


Attachments (Terms of Use)

Description Frantisek Hanzlik 2012-04-07 19:14:18 UTC
Description of problem:
I do not want any NM controlled interfaces and my kickstart file forbids NM installation with lines
-NetworkManager
-NetworkManager-gnome
-NetworkManager-gtk
-NetworkManager-openconnect
-NetworkManager-openvpn
-NetworkManager-pptp
-NetworkManager-vpnc
-evolution-NetworkManager
in %packages section (and NM really isn't installed), and my "network" keywords
specifies interfaces as:
network --onboot yes --device eth0 --bootproto static --ip 192.168.1.224 --netmask 255.255.255.0 --noipv6 --nameserver 192.168.1.254,127.0.0.1 --hostname janinka.resro.home

1) anaconda still creates interfaces with 'NM_CONTROLLED="yes"' in "/etc/sysconfig/network-scripts/ifcfg-IFACE" files
2) "network" service is not activated

Version-Release number of selected component (if applicable):
anaconda-16.25

Expected results:
- ifcfg-IFACE will have 'NM_CONTROLLED="no"'
- network service should be perhaps activated too (but not so important as 1))

Comment 1 Chris Lumens 2012-04-08 01:27:38 UTC
NetworkManager is the standard mechanism for configuring network interfaces in Fedora, and is how a part of the core installation set.  We will not be adding code to write out a separate set of network configuration just because you don't want NM.

Comment 2 Frantisek Hanzlik 2012-04-08 02:10:52 UTC
I cannot agree with You, as NetworkManager is 1) still erroneous in certain situations, and 2) often there are scenarios, where NetworkManager is useless and/or unwanted. Perhaps not only for me. Thus IMO anaconda _should_ allow configure system without NM.


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