Hide Forgot
+++ This bug was initially created as a clone of Bug #678354 +++ When trying to use VNC from a live cd I get this traceback: 16:52:15 Starting VNC... Traceback (most recent call last): File "/usr/sbin/anaconda", line 851, in <module> runVNC() File "/usr/sbin/anaconda", line 300, in runVNC vncS.startServer() File "/usr/lib64/python2.7/site-packages/pyanaconda/vnc.py", line 217, in startServer self.initialize() File "/usr/lib64/python2.7/site-packages/pyanaconda/vnc.py", line 108, in initialize dev = devices[active_devs[0]] KeyError: dbus.String(u'eth0', variant_level=1) This happens with the F14 and F15 isos. It happens in runlevel 3 and from a gnome-terminal in runlevel 5.
I got this traceback with the latest RHEL6.1 nightly: Running anaconda 13.21.111, the Red Hat Enterprise Linux system installer - please wait. 10:15:27 Starting VNC... Traceback (most recent call last): File "/usr/bin/anaconda", line 1014, in <module> runVNC() File "/usr/bin/anaconda", line 340, in runVNC vncS.startServer() File "/usr/lib/anaconda/vnc.py", line 203, in startServer self.initialize() File "/usr/lib/anaconda/vnc.py", line 104, in initialize dev = devices[active_devs[0]] KeyError: dbus.String(u'eth0', variant_level=1) install exited abnormally [1/1] The system will be rebooted when you press Ctrl-C or Ctrl-Alt-Delete. The system was processing an automated test job in Beaker. I connected to the serial console and saw that there was an error bringing up the network interface. Afte clicking OK I saw eht0 and eth1 and a usb interface I think. I selected eth0 and pressed Next. After a while I saw this traceback on the console.
Created attachment 491794 [details] syslog from the beaker
Created attachment 491795 [details] anaconda.log from the beaker
I suspect removal of HWADDR from ifcfg file (bug #690589) being responsible. From the logs it can be seen that NM tries to bring up all network devices regardless of NM_CONTROLLED and ONBOOT value and I guess this bug is a consequence of this. I confirmed with Fedora master that bringing the HWADDR value back fixes this.
*** This bug has been marked as a duplicate of bug 696127 ***