Bug 533849

Summary: Fails to enable network interface
Product: [Fedora] Fedora Reporter: Kamil Páral <kparal>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: anaconda-maint-list, sjensen, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-11-09 10:24:35 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 473303    
Description Flags
anaconda 12.44
anaconda 12.46
logs none

Description Kamil Páral 2009-11-09 09:26:56 EST
Created attachment 368216 [details]
anaconda 12.44

Description of problem:
anaconda 12.44 from 11/05 works ok, after disk partitioning a dialog to enable eth0 appears (see attachment).

anaconda 12.45 and 12.46 (from 11/08) does not display that dialog, only says that it is unable to read information from repositories (see attachment).

When I do "dhclient eth0" from console, it correctly obtains IP address and network works.

How reproducible:
Comment 1 Kamil Páral 2009-11-09 09:27:22 EST
Created attachment 368217 [details]
anaconda 12.46
Comment 2 Kamil Páral 2009-11-09 09:27:41 EST
Created attachment 368218 [details]
Comment 3 Kamil Páral 2009-11-09 10:11:42 EST
It works again with anaconda 12.46 from 11/09 boot.iso. Should I close the bug?
Comment 4 Chris Lumens 2009-11-09 10:18:54 EST
There was an anaconda-12.46-2 that went into the latest image, so yes this can likely be closed.
Comment 5 Kamil Páral 2009-11-09 10:24:35 EST
Confirmed from adamw that this issue should be fixed by the latest version bump.
Comment 6 Kamil Páral 2009-11-09 10:25:15 EST
Misclicked, setting correct status.
Comment 7 Adam Williamson 2009-11-09 10:32:24 EST
This was broken in Rawhide 20091108 boot.iso and works (confirmed by multiple testers) in 20091109. What we don't know is why...

We thought this may somehow be https://bugzilla.redhat.com/show_bug.cgi?id=533740 , which we fixed yesterday, but I can't see how. yum.log matches in both 1108 and 1109.

The fact that it works is great, but I'm a little worried about what changed...

Fedora Bugzappers volunteer triage team