Bug 755218

Summary:	Network ignores ONBOOT=yes if card is unmanaged
Product:	[Fedora] Fedora	Reporter:	redtux <mike>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	harald, iarlyy, initscripts-maint-list, jmoskovc, jonathan, jpopelka, lnykryn, notting, plautrba, robatino, rohlfing, rvokal
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-14 02:06:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description redtux 2011-11-19 16:25:06 UTC

Description of problem:


If network card is set to not be maaged by Network Manager, the system ignores ONBOOT flag


How reproducible:
start system-config-network, edit network card
check on boot and uncheck managed by Network maager


  
Actual results:
No network activated on boot

Expected results:
Network should be up

Additional info:

This functionality is needed because Network maager stops Lan and mobile Broadband working together

Comment 1 Jiri Popelka 2011-12-21 14:50:57 UTC

If you want the NIC to be activated on boot even when it's marked as NM_CONTROLLED=no, then you need to have network service enabled.

If it's not enabled (check 'systemctl status network.service') you can do that
with 'systemctl enable network.service'

Comment 2 redtux 2011-12-21 16:27:00 UTC

Network service is enabled

Comment 3 Jiri Popelka 2011-12-21 16:35:13 UTC

How does the /etc/sysconfig/network-scripts/ifcfg-<iface> look like then ?

Comment 4 redtux 2011-12-21 17:36:47 UTC

cat /etc/sysconfig/network-scripts/ifcfg-p18p1

GATEWAY=192.168.0.1
DEVICE=p18p1
BOOTPROTO=none
NETMASK=255.255.255.0
TYPE=Ethernet
HWADDR=00:01:6c:0d:a1:93
IPADDR=192.168.0.2
NM_CONTROLLED=no
IPV6INIT=no
PREFIX=24
ONBOOT=yes
USERCTL=yes

Comment 5 Bill Nottingham 2011-12-21 19:30:24 UTC

What is the status of the network service?

Comment 6 redtux 2011-12-21 20:27:28 UTC

always running

Comment 7 redtux 2011-12-22 16:01:08 UTC

This is from syslog

Dec 22 08:10:14 redtux NetworkManager[904]:    ifcfg-rh:     read connection 'System p18p1'
Dec 22 08:10:14 redtux NetworkManager[904]: NetworkManager[904]:    ifcfg-rh:     read connection 'System p18p1'
Dec 22 08:10:14 redtux NetworkManager[904]:    ifcfg-rh: Ignoring connection 'System p18p1' and its device due to NM_CONTROLLED/BRIDGE/VLAN.
Dec 22 08:10:14 redtux NetworkManager[904]: NetworkManager[904]:    ifcfg-rh: Ignoring connection 'System p18p1' and its device due to NM_CONTROLLED/BRIDGE/VLAN.

Comment 8 Bill Nottingham 2012-01-03 19:03:55 UTC

What is the output of 'systemctl status network.service'?

Comment 9 Torsten Rohlfing 2012-10-12 18:45:38 UTC

I believe I am seeing this exact problem on F17, but only on machines that were installed from scratch. Machines upgraded from F15 or F16 are not showing this problem.

Like the posts above, my cards are labelled "ONBOOT=yes" and "NM_CONTROLELD=no", network service is enabled and running, but the cards are not brought up during boot - only when I manually start the network service again from the command line.

Comment 10 Fedora End Of Life 2013-02-14 02:06:54 UTC

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.