Bug 866454 - anaconda claims I have no network devices
Summary: anaconda claims I have no network devices
Keywords:
Status: CLOSED DUPLICATE of bug 866434
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F18Beta, F18BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2012-10-15 12:10 UTC by Kamil Páral
Modified: 2012-10-15 14:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-15 14:43:24 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
anaconda screenshot (23.43 KB, image/png)
2012-10-15 12:10 UTC, Kamil Páral 		no flags Details
anaconda.log (2.02 KB, text/plain)
2012-10-15 12:11 UTC, Kamil Páral 		no flags Details
anaconda-yum.conf (325 bytes, text/plain)
2012-10-15 12:11 UTC, Kamil Páral 		no flags Details
ifcfg.log (641 bytes, text/plain)
2012-10-15 12:11 UTC, Kamil Páral 		no flags Details
packaging.log (1.19 KB, text/plain)
2012-10-15 12:11 UTC, Kamil Páral 		no flags Details
program.log (31.29 KB, text/plain)
2012-10-15 12:11 UTC, Kamil Páral 		no flags Details
storage.log (53.78 KB, text/plain)
2012-10-15 12:11 UTC, Kamil Páral 		no flags Details
syslog (69.12 KB, text/plain)
2012-10-15 12:11 UTC, Kamil Páral 		no flags Details
X.log (55.62 KB, text/plain)
2012-10-15 12:11 UTC, Kamil Páral 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 866434 0 unspecified CLOSED DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.0 was not provided by any .service files 2021-02-22 00:41:40 UTC

Internal Links: 866434

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 ***
Note You need to log in before you can comment on or make changes to this bug.