Bug 466553
Summary: | nm-system-settings ifcfg-fedora fails to parse ifcfg-ethX files for dhcp correctly | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | David Cantrell <dcantrell> |
Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | rawhide | CC: | clumens, dcbw, maurizio.antillon, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-10-11 02:52:01 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
David Cantrell
2008-10-10 21:18:44 UTC
I have modified loader to write the new ifcfg-DEVICE file in a temporary directory, then move it in to /etc/sysconfig/network-scripts, but that has not changed anything. Just trying different ideas. Also worth noting that if you choose manual network configuration in loader, NetworkManager runs along just fine and the interface is brought up. Until we come up with a solution, this problem is preventing DHCP from being used during installation. Correcting previous information, NetworkManager output goes to tty4 during installation. I keep seeing device state change when I try a DHCP install. Device state change goes from 8 to 3, which I think is from NM_DEVICE_STATE_ACTIVATED to NM_DEVICE_STATE_UNAVAILABLE. Could this be the fault of dhclient or something else on the system? As stated before, static IP configuration is working fine. OK, now I'm completely confused. After making more changes to anaconda, things appear to be working now. I can't recreate the problem I was having, so I'm going to call this whole issue a problem on the anaconda side. chris, were you able to reproduce this at all today? I added some bits to NM svn4174 so NM will tell you why it's deactivating the interface, so in that case we were looking at on Friday we should be able to figure out why NM was doing what it was. |