Bug 806466 - Network connections not up OOTB after non-network install in 17 Beta RC1
Summary: Network connections not up OOTB after non-network install in 17 Beta RC1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 17
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedNTH RejectedBlocker
Depends On:
Blocks: F17Beta-accepted, F17BetaFreezeExcept
TreeView+ depends on / blocked
 
Reported: 2012-03-23 20:36 UTC by Adam Williamson
Modified: 2012-04-11 17:22 UTC (History)
8 users (show)

Fixed In Version: anaconda-17.20-1.fc17
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-11 17:22:25 UTC


Attachments (Terms of Use)
anaconda ifcfg log from an offending install (1.76 KB, text/plain)
2012-03-26 18:30 UTC, Adam Williamson
no flags Details

Description Adam Williamson 2012-03-23 20:36:35 UTC
17 Beta RC1 seems to have regressed things to the pre-Fedora 16 state where network interfaces were not up OOTB after a non-network install. This was longstanding behaviour but we actually changed it in 16:

https://bugzilla.redhat.com/show_bug.cgi?id=498207

so we wrote ONBOOT=yes even when installing not from the network. We should probably go ahead and carry on doing that with Fedora 17. Not sure if we should consider this a blocker, but nominating as both blocker and NTH just so we can kick it around.

Comment 1 Adam Williamson 2012-03-24 20:47:47 UTC

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 2 Adam Williamson 2012-03-24 20:48:12 UTC
note: will wanted the ifcfg log from an install to investigate this one.

Comment 3 Adam Williamson 2012-03-26 17:45:51 UTC
Discussed at 2012-03-26 QA meeting acting as a blocker review meeting. As the impact of this bug combined with 806664 is broadly the same as #804716 for TC2, and we took 804716 as NTH, we agreed that this bug and 806664 should be accepted as NTH but rejected as blockers.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 4 Adam Williamson 2012-03-26 18:30:39 UTC
Created attachment 572835 [details]
anaconda ifcfg log from an offending install

Comment 5 Will Woods 2012-03-27 19:25:33 UTC
Additional info needed:
- GUI or text install?
- Kickstart or no?
- What was the boot device / install source?
- What network devices were configured (if any), and how (boot cmdline, kickstart, GUI)?
- What ifcfg files do exist, if any? What are their ONBOOT settings?

Comment 6 Adam Williamson 2012-03-27 19:30:09 UTC
the case I'm certain reproduces the bug is a minimal interactive GUI install from DVD in a stock virt-manager VM. No network device configured during boot. I think a network install also reproduces but I'm not 100% sure.

an ifcfg-eth0 file is created, which specifies ONBOOT=no.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 7 Adam Williamson 2012-03-27 19:30:33 UTC
s/during boot/during install/g.

Comment 8 Bill Nottingham 2012-03-28 20:24:51 UTC
This also happened for me with a live image install.

Comment 9 Fedora Update System 2012-04-04 00:26:25 UTC
anaconda-17.17-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/anaconda-17.17-1.fc17

Comment 10 Andre Robatino 2012-04-04 16:53:09 UTC
Confirmed that network is up OOTB on minimal i386 and x86_64 DVD installs of 17 Beta RC3. The ifcfg-* file has ONBOOT="yes".

Comment 11 Adam Williamson 2012-04-04 22:13:42 UTC
Ditto Andre, on both minimal and desktop. Yay!



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 12 Fedora Update System 2012-04-05 18:27:26 UTC
Package anaconda-17.17-1.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-17.17-1.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-5388/anaconda-17.17-1.fc17
then log in and leave karma (feedback).

Comment 13 Fedora Update System 2012-04-06 13:58:38 UTC
anaconda-17.19-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/anaconda-17.19-1.fc17

Comment 14 Fedora Update System 2012-04-10 04:14:34 UTC
anaconda-17.20-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/anaconda-17.20-1.fc17

Comment 15 Fedora Update System 2012-04-11 17:22:25 UTC
anaconda-17.20-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.


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