Bug 684423

Summary:	ifdown cannot find sit devices.
Product:	[Fedora] Fedora	Reporter:	tim <tim>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	14	CC:	iarlyy, iprikryl, jonathan, jpopelka, notting, plautrba, rvokal, tim, vpavlin
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:	2012-07-20 10:26:15 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 tim 2011-03-12 13:02:44 UTC

Description of problem:

ifdown reports it cannot find device sit1 after successfully bringing it up with ifup. When directly using /etc/sysconfig/network-scripts/ifdown-sit, there is no problem and ifconfig no longer shows the sit1 interface.

# ifup sit1 && echo success
success
# ifdown sit1 && echo success
Error: Device 'sit1' not found.
# /etc/sysconfig/network-scripts/ifdown-sit sit1 && echo success
success


Version-Release number of selected component (if applicable):
Not sure if is actually is net-tools, but I have net-tools-1.60-105.fc14.1(i686)

/sbin/ifdown script itself does not seem to have a version or revision number of any kind.
/etc/sysconfig/network-scripts/ifdown-sit shows a verion number of 2002-11-01.

How reproducible:
Always

Steps to Reproduce:
1. Configure an ipv6 tunnel device 'sit1'
2. Bring it up using ifup sit1
3. Check it is up using ifconfig
4. Try to bring it down using ifdown sit1
5. Check that is possible to bring it down using /etc/sysconfig/network-scripts/ifdown-sit sit1
6. Check it is indeed down, using ifconfig

Comment 1 tim 2011-03-12 14:11:45 UTC

It seems that the problem only occurs if NetworkManager is active. Because when I do:
# service NetworkManager stop
# ifdown sit1

Now ifdown does not return an error message and checking with ifconfig shows that the interface is indeed down.

Also service network restart signals no more problems if NetworkManager is not running. It seems that NetworkManager is conflicting with the 'normal' network scripts.

Maybe I'm doing something wrong and this isn't really a bug, but as I doubt that the sit1 interface is NetworkManager controlled, I don't think it should interfere with the correct functionality of ifup & ifdown and even if it did, it escapes me why ifup sit1 works as expected while ifdown sit1 does not. (ifdown lo seems to have the same problem by the way)

I consider this a problem, because I'm trying to see if I can replace the older Fedora 10 on my server with F14 and get ipv6/ipv4 dual stack working on my network while I'm at it, but for that I need to be sure that the network interfaces are correctly initiated during boot and while I have NetworkManager enabled, this seems to be a problem, because sit1 is not automatically getting up during a service network start while NetworkManager is active.

So, if not a bug, could this be transformed into a change request?

Comment 2 Bill Nottingham 2011-03-14 15:13:33 UTC

Does this fix it for you?

http://git.fedorahosted.org/git/?p=initscripts.git;a=commitdiff;h=bec37b082a490e101799810fe210aa273ad26de3