Bug 866454

Summary: anaconda claims I have no network devices
Product: [Fedora] Fedora Reporter: Kamil Páral <kparal>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: anaconda-maint-list, g.kaviyarasu, jonathan, rvykydal, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-15 14:43:24 UTC Type: Bug
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: 752660    
Attachments:
Description Flags
anaconda screenshot
none
anaconda.log
none
anaconda-yum.conf
none
ifcfg.log
none
packaging.log
none
program.log
none
storage.log
none
syslog
none
X.log none

Description Kamil Páral 2012-10-15 12:10:40 UTC
Created attachment 627366 [details]
anaconda screenshot

Description of problem:
Sometimes anaconda claims I have no network devices. But if I switch to tty2, I see in "ip a" output that I have eth0 with IP address assigned and ping and scp works.

I haven't seen this problem in Beta TC3.

Version-Release number of selected component (if applicable):
F18 Beta TC4 DVD i486
anaconda 18.16
VM

How reproducible:
sometimes

Comment 1 Kamil Páral 2012-10-15 12:11:20 UTC
Created attachment 627369 [details]
anaconda.log

Comment 2 Kamil Páral 2012-10-15 12:11:25 UTC
Created attachment 627370 [details]
anaconda-yum.conf

Comment 3 Kamil Páral 2012-10-15 12:11:27 UTC
Created attachment 627371 [details]
ifcfg.log

Comment 4 Kamil Páral 2012-10-15 12:11:30 UTC
Created attachment 627372 [details]
packaging.log

Comment 5 Kamil Páral 2012-10-15 12:11:34 UTC
Created attachment 627373 [details]
program.log

Comment 6 Kamil Páral 2012-10-15 12:11:40 UTC
Created attachment 627374 [details]
storage.log

Comment 7 Kamil Páral 2012-10-15 12:11:46 UTC
Created attachment 627375 [details]
syslog

Comment 8 Kamil Páral 2012-10-15 12:11:49 UTC
Created attachment 627376 [details]
X.log

Comment 9 Kamil Páral 2012-10-15 12:15:06 UTC
This probably doesn't fulfill this criterion:
 The installer must be able to use at least one of the HTTP or FTP remote package source options 
https://fedoraproject.org/wiki/Fedora_18_Alpha_Release_Criteria

I think all of these TC4 bugs are somehow related to bug 866434, which seems to be a NM fault.

Comment 10 Radek Vykydal 2012-10-15 12:59:33 UTC
(In reply to comment #9)
 
> I think all of these TC4 bugs are somehow related to bug 866434, which seems
> to be a NM fault.

Yes, the same NM crash as in bug 866434 can be found in syslog.

Comment 11 Chris Lumens 2012-10-15 14:43:24 UTC

*** This bug has been marked as a duplicate of bug 866434 ***