Bug 870583 - NetworkManager fails to set up eth0 using dhcp on Fedora ARM ()
Summary: NetworkManager fails to set up eth0 using dhcp on Fedora ARM ()
Keywords:
Status: CLOSED DUPLICATE of bug 870608
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 17
Hardware: arm
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-27 01:59 UTC by Mildred
Modified: 2012-10-31 12:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-31 12:03:03 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Mildred 2012-10-27 01:59:04 UTC 
Description of problem: When booting the fedora arm image (inside a LXC container inside a debian), I get the following error:

network[82]: Bringing up loopback interface:  [  OK  ]
network[82]: Bringing up interface eth0:
network[82]: (process:228): GLib-WARNING **: (gerror.c:390):g_error_new_valist: runtime check failed: (domain != 0)
network[82]: Error: No suitable device found: no device found for connection 'System eth0'.
network[82]: [FAILED]

I get the same error with nmcli:

[root@fedora-arm etc]# nmcli con up id 'System eth0'

(process:293): GLib-WARNING **: (gerror.c:390):g_error_new_valist: runtime check failed: (domain != 0)
Error: No suitable device found: no device found for connection 'System eth0'.



Version-Release number of selected component (if applicable):
Fedora-ARM downloaded from http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/arm/Fedora-17-arm-console.tar.xz (no updates yet)

How reproducible: always
Comment 1 Jirka Klimes 2012-10-31 12:03:03 UTC 

*** This bug has been marked as a duplicate of bug 870608 ***
Note You need to log in before you can comment on or make changes to this bug.