Bug 587030 - /etc/sysconfig/network-scripts/Auto_SIDNAME files cause networking scripts to barf
/etc/sysconfig/network-scripts/Auto_SIDNAME files cause networking scripts to...
Product: Fedora
Classification: Fedora
Component: initscripts (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-04-28 13:51 EDT by Wolfgang Rupprecht
Modified: 2014-03-16 23:23 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-04-28 14:57:27 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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

  None (edit)
Description Wolfgang Rupprecht 2010-04-28 13:51:25 EDT
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):

How reproducible:

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 13:56:26 EDT
Created attachment 409924 [details]
boot.log fragment showing the initscripts parse failure
Comment 2 Bill Nottingham 2010-04-28 14:35:11 EDT
This is fixed in F-13. It's an awful large set to backport, though.
Comment 3 Wolfgang Rupprecht 2010-04-28 14:39:03 EDT
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.