Bug 53355

Summary: ifdown-ipv6 tries to sysctl unknown keys
Product: [Retired] Red Hat Linux Reporter: Pekka Savola <pekkas>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED RAWHIDE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-01-25 04:14:50 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:
Attachments:
Description Flags
only try to set sysctl values if the corresponding device still exists none

Description Pekka Savola 2001-09-07 09:05:24 UTC 
Under certain, unclear scenarios (this has come up two-three times, but
I've never
managed to pin it down, no matter what), when doing 'ifdown <ipv6-device>' 
you get like:

error: 'net.ipv6.conf.sit0.forwarding' is an unknown key
error: 'net.ipv6.conf.sit0.accept_ra' is an unknown key
error: 'net.ipv6.conf.sit0.accept_redirects' is an unknown key

, because the interface has already been deleted. A good (open) question
is, why this
only happens rather rarely.

These should probably be hidden.  It can be done with the attached patch.
Comment 1 Pekka Savola 2001-09-07 09:06:09 UTC 
Created attachment 31215 [details]
only try to set sysctl values if the corresponding device still exists
Comment 2 Bill Nottingham 2002-04-12 20:31:28 UTC 
This has to be fixed by now. In any case, 6.63-1 will add '-e' to all the
invocations.