Description of problem: Following traceback appears when anaconda is trying to start vnc server: Running anaconda 16.17, the Fedora system installer - please wait. 08:06:54 Starting VNC... Traceback (most recent call last): File "/usr/sbin/anaconda", line 715, in <module> setupDisplay(anaconda, opts) File "/usr/sbin/anaconda", line 532, in setupDisplay runVNC(vncS) File "/usr/sbin/anaconda", line 281, in runVNC vncS.startServer() File "/usr/lib64/python2.7/site-packages/pyanaconda/vnc.py", line 198, in startServer self.initialize() File "/usr/lib64/python2.7/site-packages/pyanaconda/vnc.py", line 105, in initialize devname = devices[active_devs[0]].iface KeyError: dbus.String(u'eth0', variant_level=1) boot parameters: -bash-4.2# cat /proc/cmdline root=/dev/ram0 ro ip=off ramdisk_size=40000 cio_ignore=all,!0.0.0009 CMSDASD=191 CMSCONFFILE=e40.conf vnc _escue Version-Release number of selected component (if applicable): anaconda-16.17 How reproducible: always Steps to Reproduce: 1. start the installation with "vnc" boot parameter 2. connect via ssh to continue with the install 3. select language 4. wait for vnc server to start Actual results: traceback Expected results: vnc server starts successfully Additional info: workaround_1: do not use "vnc" boot parameter workaround_2: use "vnc ksdevice=eth0" boot parameters
Created attachment 523972 [details] anaconda.log
Created attachment 523973 [details] syslog
Proposed patch: https://www.redhat.com/archives/anaconda-devel-list/2011-September/msg00154.html
This should be fixed in F17.
Retested with anaconda-17.29, this issue is fixed, vnc installation finished without any traceback. Closing this bug.