Bug 965841 - anaconda no longer creates /etc/sysconfig/network, systems without NetworkManager do not bring up network
Summary: anaconda no longer creates /etc/sysconfig/network, systems without NetworkMan...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 19
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Radek Vykydal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException
: 972353 (view as bug list)
Depends On:
Blocks: F19-accepted, F19FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2013-05-21 20:21 UTC by Orion Poplawski
Modified: 2013-06-12 21:48 UTC (History)
9 users (show)

Fixed In Version: anaconda-19.30.1-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-12 21:48:36 UTC


Attachments (Terms of Use)

Description Orion Poplawski 2013-05-21 20:21:00 UTC
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):
19.28-1

See also bug 895900 (which is very hard to read).

Comment 1 Radek Vykydal 2013-05-22 08:33:11 UTC
I have a patch for this issue (bug 957897) to be included post Beta.

Comment 2 Adam Williamson 2013-05-30 01:58:32 UTC
It's now post-Beta. This looks like something we'd definitely want to fix for final, so nominating as freeze exception.

Comment 3 Adam Williamson 2013-05-30 18:18:47 UTC
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.

Comment 4 Orion Poplawski 2013-06-11 02:54:01 UTC
Confirmed that this is fixed in 19.30.3

Comment 5 Adam Williamson 2013-06-12 02:08:13 UTC
*** Bug 972353 has been marked as a duplicate of this bug. ***

Comment 6 Adam Williamson 2013-06-12 21:48:36 UTC
19.30.3 has been pushed stable, so closing.


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