Bug 587030 - /etc/sysconfig/network-scripts/Auto_SIDNAME files cause networking scripts to barf
Summary: /etc/sysconfig/network-scripts/Auto_SIDNAME files cause networking scripts to...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-28 17:51 UTC by Wolfgang Rupprecht
Modified: 2014-03-17 03:23 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-28 18:57:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
boot.log fragment showing the initscripts parse failure (836 bytes, text/plain)
2010-04-28 17:56 UTC, Wolfgang Rupprecht
no flags Details

Description Wolfgang Rupprecht 2010-04-28 17:51:25 UTC
Description of problem:

The initscripts in /etc/sysconfig/network-scripts/ do not ignore the ifcfg-Auto_SIDNAME files.

Version-Release number of selected component (if applicable):
initscripts-9.02.1-1.x86_64

How reproducible:
always

Steps to Reproduce:
1. Run NetworkManager (default)
2. add an automatic WIFI entry to be run at boot-time
3. stop running NetworkManager and run networking instead
4. reboot
5. notice the networking init scripts barf when they get to the ifcfg-Auto_XXXX name.
  
Actual results:
Lots of gripes about a shell-script in pain.

Expected results:
No gripes.

Additional info:
The ifcfg-Auto_XXXX files should probably just be ignored.  Alternately perhaps a field for NM_CONTROLLED=yes could be added to the file.

Comment 1 Wolfgang Rupprecht 2010-04-28 17:56:26 UTC
Created attachment 409924 [details]
boot.log fragment showing the initscripts parse failure

Comment 2 Bill Nottingham 2010-04-28 18:35:11 UTC
This is fixed in F-13. It's an awful large set to backport, though.

Comment 3 Wolfgang Rupprecht 2010-04-28 18:39:03 UTC
no problem.  I just didn't want this to fall through the cracks.  Feel free to close the bug.


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