Red Hat Bugzilla – Bug 853584
Minimum install not creating /etc/sysconfig/network and /etc/sysconfig/network-scripts/ifcfg-<interface>
Last modified: 2012-11-28 06:49:29 EST
Description of problem:
Installing from x86_64 netinstall F18 TC4. After installation, no /etc/sysconfig/network is created. In addition, /etc/sysconfig/network-scripts/ifcfg-eth0 (or pp1p1 for example) are not created, though ifcfg-lo is created.
Version-Release number of selected component (if applicable):
Fedora-18 netinstall-TC4 is the only one I've tested.
Download netinstall iso and choose minimum install
Steps to Reproduce: See above
Actual results: There is no /etc/sysconfig/network file created. Nor is there an /etc/sysconfig/network-scripts/ifcfg-eth0 or other interface created.
To have an /etc/sysconfig/network and /etc/sysconfig/network-scripts/ifcfg-eth0 (or pp1p1,etc.).
Additional info: Despite these missing files,if one uses the default Network Manager, the interface will be started and get an address at boot. Therefore, it may only affect people who prefer to avoid NetworkManager (and it now takes deliberate effort to do so.)
Problem still exists in TC5
This should be fixed on master with
(In reply to comment #2)
> This should be fixed on master with
> commit e2307897400700b10d60b0a80e7b15ef7d6f1772
Just a note - also next 6 (or et least 4) patches from master should be included.
This is still happening with pretc6. (I've not been keeping track of commit numbers, just giving TC's a quick install when they're out.)
Not fixed in tcpre7-1
Just tried pretc7-2 (the one labeled F17). :)
Still not fixed. When will the commit in comment #3 be applied?
Not fixed in latest Gold Alpha.
Is this expected to be fixed by Beta?
*** Bug 858962 has been marked as a duplicate of this bug. ***
This seems to be fixed in Beta TC1. I wasn't able to boot into multi-user mode in this beta, but when I booted single user mode, the files existed. Thank you.
*** Bug 877764 has been marked as a duplicate of this bug. ***
This bug looks to have been fixed for many anaconda builds now but missed being closed. If you find you are still experiencing it with Fedora 18 Beta (RC1) or later, please re-open the bug.
(ref comment #10)