Bug 806466
| Summary: | Network connections not up OOTB after non-network install in 17 Beta RC1 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Williamson <awilliam> | ||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 17 | CC: | anaconda-maint-list, g.kaviyarasu, jonathan, notting, robatino, satellitgo, vanmeeuwen+fedora, wwoods | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | AcceptedNTH RejectedBlocker | ||||||
| Fixed In Version: | anaconda-17.20-1.fc17 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-04-11 17:22:25 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 752652 | ||||||
| Attachments: |
|
||||||
|
Description
Adam Williamson
2012-03-23 20:36:35 UTC
-- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers note: will wanted the ifcfg log from an install to investigate this one. 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 Created attachment 572835 [details]
anaconda ifcfg log from an offending install
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? 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 s/during boot/during install/g. This also happened for me with a live image install. anaconda-17.17-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/anaconda-17.17-1.fc17 Confirmed that network is up OOTB on minimal i386 and x86_64 DVD installs of 17 Beta RC3. The ifcfg-* file has ONBOOT="yes". Ditto Andre, on both minimal and desktop. Yay! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers 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). anaconda-17.19-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/anaconda-17.19-1.fc17 anaconda-17.20-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/anaconda-17.20-1.fc17 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. |