Bug 613803

Summary:	ip / ifconfig appears to not work in single-user mode
Product:	[Fedora] Fedora	Reporter:	Need Real Name <lsof>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	13	CC:	dwalsh, iarlyy, iprikryl, jonathan, jpopelka, mgrepl, notting, plautrba, rvokal
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:	2010-07-13 16:32:03 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 Need Real Name 2010-07-12 20:46:20 UTC

1. Boot into runlevel 1
2. Edit /etc/sysconfig/network-scripts/ifcfg-eth0, and change NM_CONTROLLED=yes to NM_CONTROLLED=no
3. /etc/init.d/networking restart
4. ifconfig

(no output)

5. ifconfig -a

(no output)

6. ping 1.2.3.4

(I get output)

7. ip addr

(no output)

Something is going wrong here... same as if I run with ifup eth0

Comment 1 Jiri Popelka 2010-07-13 12:12:46 UTC

Steps to reproduce:

1. telinit 1

2. 'ip a' or 'ifconfig -a'
(no output)

3. setenforce 0

4. 'ip a' or 'ifconfig -a'
(work as expected)

Comment 2 Daniel Walsh 2010-07-13 12:31:36 UTC

This is a known problem, which we are changing by forcing the running of sulogin.

If you execute sulogin, the terminals will work correctly.

Or you can do a little trick by executing

ip a | cat

Comment 3 Bill Nottingham 2010-07-13 16:32:03 UTC

Actually, we're not forcing sulogin, but we're putting another command in between so policy can work.

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