Bug 530203 - NetworkManager fails to acquire DHCP address during installation
Summary: NetworkManager fails to acquire DHCP address during installation
Keywords:
Status: CLOSED DUPLICATE of bug 453404
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-21 20:51 UTC by Pierre Ossman
Modified: 2009-10-26 22:25 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-10-26 22:25:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Pierre Ossman 2009-10-21 20:51:18 UTC
This has been an issue since NM was introduced in the installer, but here is yet another report that NM doesn't work in the F12 beta either. Neither static nor dynamic configuration works and only spew out "Error configuring network device".

There is nothing wrong with the network and manually starting the network using ifconfig or dhclient works just fine. Unfortunately there doesn't seem to be a way to tell NM to go sit in the corner and let me configure the network manually, so right now the netinstall iso only serves any meaningful purpose as a coaster.

Comment 1 Dan Williams 2009-10-23 18:07:01 UTC
Please try http://koji.fedoraproject.org/koji/buildinfo?buildID=137758 which fixes the static IP bug (bug 528068); I'm curious about the DHCP issue, that I haven't seen and haven't heard of reported yet.

Can you grab some of the NM spew off one of the VTs?

Comment 2 Dan Williams 2009-10-23 18:08:54 UTC
Note that that build is already in f12/rawhide, so you should be able be able to grab a new netinstall iso.  Yesterday's install certainly configured the network OK for me with DHCP for me in a VM.

Comment 3 Pierre Ossman 2009-10-23 20:04:09 UTC
I couldn't see any NM stuff in any VT, only stuff from nm-system-settings. Where should the output be going?

Where do I find new isos?

Comment 4 Dan Williams 2009-10-23 20:15:07 UTC
from nm-system-settings?  what kind of stuff?  BTW in NM 0.8 (f12+) nm-system-settings is merged into NM, so you should see stuff like:

NetworkManager:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-pan0 ... 
NetworkManager:    ifcfg-rh:     read connection 'System pan0'
NetworkManager:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-Auto_eth0 ... 
NetworkManager:    ifcfg-rh:     read connection 'Auto eth0'
NetworkManager:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-Test_LEAP ... 
NetworkManager:    ifcfg-rh:     error: Missing LEAP identity
NetworkManager:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-Test_WPA_TLS ... 
NetworkManager:    ifcfg-rh:     read connection 'Test WPA TLS'

instead of

nm-system-settings:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/blahblah

Comment 6 Pierre Ossman 2009-10-23 20:56:37 UTC
(In reply to comment #4)
> from nm-system-settings?  what kind of stuff?  BTW in NM 0.8 (f12+)
> nm-system-settings is merged into NM, so you should see stuff like:
> 
> NetworkManager:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-pan0
> ... 
> NetworkManager:    ifcfg-rh:     read connection 'System pan0'
> NetworkManager:    ifcfg-rh: parsing
> /etc/sysconfig/network-scripts/ifcfg-Auto_eth0 ... 

Something like that, yes.

I'll try to make an attempt tomorrow and see what happens.

Comment 7 Dan Williams 2009-10-23 22:14:16 UTC
Ok, thanks, let me know!

Comment 8 Dan Williams 2009-10-23 22:14:31 UTC
Ok, thanks, let me know!

Comment 9 Pierre Ossman 2009-10-24 13:18:03 UTC
Still broken.

It seems like things have to work on the first attempt, or you're screwed. It actually works if it is able to get a dhcp lease on the first go. But if that fails, a second attempt does nothing.

Looking at the log, it stops at "ifcfg-rh: updating yadda-yadda/ifcfg-eth0". It makes no attempt to start dhclient and actually get a lease.

Comment 10 Dan Williams 2009-10-26 22:25:01 UTC
Yes, if NM doesn't get a lease, it will fall back to whatever other wired connection it can try.  In this case, there isn't one.  There's bugs for that already, mind if I dupe?

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


Note You need to log in before you can comment on or make changes to this bug.