Bug 514501
Summary: | dbus.exceptions.DBusException: org.freedesktop.Hal.NoSuchDevice: No device with id /org/freedesktop/NetworkManager/Devices/0 | |||
---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | James Laska <jlaska> | |
Component: | anaconda | Assignee: | Chris Lumens <clumens> | |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | |
Severity: | high | Docs Contact: | ||
Priority: | low | |||
Version: | rawhide | CC: | dcbw, harald, hristozov, jturner, norrist, rmaximo, vanmeeuwen+fedora, walters | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 524793 525433 (view as bug list) | Environment: | ||
Last Closed: | 2009-08-03 14:41: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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 507676, 525433 |
Description
James Laska
2009-07-29 12:34:43 UTC
Adding Dan Williams to the cc list for guidance. Perhaps related to recent NM changes? clumens and I are on it... This should be fixed in the next build of anaconda, though there are later problems in network.py that need to be looked at. I'm going to save those for David... We're now seeing the udev db having only very minimal information for eth0 (at least on my kvm tests) unless we run udev_trigger(subsystem="net") twice and early on. The first run is not enough to populate the database with the ID_{MODEL,VENDOR}_FROM_DATABASE keys nor to add the /dev/.udev/db/ entry that we require to do anything. Running a second time immediately after the first will add this information, however. You can see the logging results at: http://clumens.fedorapeople.org/syslog There are two references to SETTLE, one after each run of udev_trigger, to help break up the log file output. Harald - any suggestions you can provide on what could be going wrong here? I'd be happy to explain further about the environment we're in, or to test something for you. I just don't know where to look at what could possibly be happening. *** Bug 514829 has been marked as a duplicate of this bug. *** Well, I hope you are reading the udev database via libudev ... Appears to be fixed in installation images from 2009-08-01 I'm also not seeing it anymore. |