Red Hat Bugzilla – Bug 965841
anaconda no longer creates /etc/sysconfig/network, systems without NetworkManager do not bring up network
Last modified: 2013-06-12 17:48:36 EDT
Description of problem:
anaconda no longer creates /etc/sysconfig/network. This means that systems without NetworkManager do not bring up the network without:
echo NETWORKING=yes > /etc/sysconfig/network
Version-Release number of selected component (if applicable):
See also bug 895900 (which is very hard to read).
I have a patch for this issue (bug 957897) to be included post Beta.
It's now post-Beta. This looks like something we'd definitely want to fix for final, so nominating as freeze exception.
Discussed at 2013-05-30 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-05-30/f19final-blocker-review-1.1.2013-05-30-16.02.log.txt . Accepted as a freeze exception issue: this might be blocker if minimal installs still used network.service by default, but they don't. Still, this could be bad for people who are using a kickstart to install without NM.
Confirmed that this is fixed in 19.30.3
*** Bug 972353 has been marked as a duplicate of this bug. ***
19.30.3 has been pushed stable, so closing.