Bug 514501 - dbus.exceptions.DBusException: org.freedesktop.Hal.NoSuchDevice: No device with id /org/freedesktop/NetworkManager/Devices/0
Summary: dbus.exceptions.DBusException: org.freedesktop.Hal.NoSuchDevice: No device wi...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 514829 (view as bug list)
Depends On:
Blocks: F12Alpha, F12AlphaBlocker 525433
TreeView+ depends on / blocked
 
Reported: 2009-07-29 12:34 UTC by James Laska
Modified: 2013-09-02 06:37 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 524793 525433 (view as bug list)
Environment:
Last Closed: 2009-08-03 14:41:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description James Laska 2009-07-29 12:34:43 UTC
Description of problem:

Attempting to verify the fix for bug#511907 results in an exception while transitioning to stage#2.  This occurs in a text-mode or graphical (vnc/gui) install.

Version-Release number of selected component (if applicable):

* anaconda-12.5

How reproducible:

 * everytime

Steps to Reproduce:
1. Boot the installer for rawhide-20090728
2. Enter lang+keymap
3. Choose a URL installation
  
Actual results:

Running anaconda 12.5, the Fedora system installer - please wait.              
12:12:19 Starting VNC...
ERROR:dbus.proxies:Introspect error on :1.1:/org/freedesktop/NetworkManager/Devices/0: dbus.exceptions.DBusException: org.freedesktop.Hal.NoSuchDevice: No device with id /org/freedesktop/NetworkManager/Devices/0
Traceback (most recent call last):
  File "/usr/bin/anaconda", line 868, in <module>
    runVNC()
  File "/usr/bin/anaconda", line 353, in runVNC
    vncS.startServer()
  File "/usr/lib/anaconda/vnc.py", line 208, in startServer
    self.initialize()
  File "/usr/lib/anaconda/vnc.py", line 102, in initialize
    netinfo = network.Network()
  File "/usr/lib/anaconda/network.py", line 342, in __init__
    available_devices = self.available()
  File "/usr/lib/anaconda/network.py", line 393, in available
    self.netdevices[dev].set(('DESC', isys.getNetDevDesc(dev)))
  File "/usr/lib/anaconda/isys.py", line 599, in getNetDevDesc
    device_props = device_iface.get_dbus_method("GetAllProperties")()
  File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 630, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.Hal.NoSuchDevice: No device with id /org/freedesktop/NetworkManager/Devices/0
install exited abnormally [1/1] 
disabling swap...
unmounting filesystems...
	/mnt/runtime done
	disabling /dev/loop0 LOOP_CLR_FD failed: 16
	/proc done
	/dev/pts done
	/sys done
	/selinux done
sending termination signals...done
sending kill signals...done
you may safely reboot your system


Expected results:

Stage#2 starts successfully.

Additional info:

 * This defect is preventing additional testing of F12 Alpha
 * Marking this as severity=high based on http://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow#Severity

Comment 1 James Laska 2009-07-29 13:55:29 UTC
Adding Dan Williams to the cc list for guidance.  Perhaps related to recent NM changes?

Comment 2 Dan Williams 2009-07-29 15:55:47 UTC
clumens and I are on it...

Comment 3 Chris Lumens 2009-07-29 19:09:49 UTC
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...

Comment 4 Chris Lumens 2009-07-30 17:07:53 UTC
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.

Comment 5 Chris Lumens 2009-07-30 17:50:01 UTC
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.

Comment 6 Todd 2009-07-31 02:41:11 UTC
*** Bug 514829 has been marked as a duplicate of this bug. ***

Comment 7 Harald Hoyer 2009-07-31 08:00:53 UTC
Well, I hope you are reading the udev database via libudev ...

Comment 8 Todd 2009-08-01 20:34:29 UTC
Appears to be fixed in installation images from 2009-08-01

Comment 9 Andy Lindeberg 2009-08-03 14:41:01 UTC
I'm also not seeing it anymore.


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