Bug 739846 - Traceback when starting the installation with "vnc" parameter on s390x
Summary: Traceback when starting the installation with "vnc" parameter on s390x
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 16
Hardware: s390x
OS: Linux
Target Milestone: ---
Assignee: Radek Vykydal
QA Contact: Fedora Extras Quality Assurance
Depends On: 733680
Blocks: ZedoraTracker
TreeView+ depends on / blocked
Reported: 2011-09-20 08:17 UTC by Jan Stodola
Modified: 2012-06-29 12:14 UTC (History)
4 users (show)

Fixed In Version: anaconda-17.1-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-06-29 12:14:46 UTC
Type: ---

Attachments (Terms of Use)
anaconda.log (3.76 KB, text/plain)
2011-09-20 08:18 UTC, Jan Stodola
no flags Details
syslog (26.78 KB, text/plain)
2011-09-20 08:19 UTC, Jan Stodola
no flags Details

System ID Priority Status Summary Last Updated
Red Hat Bugzilla 541873 medium CLOSED Cannot download kickstart from nfs on s390x 2020-10-14 00:28:05 UTC

Internal Links: 541873

Description Jan Stodola 2011-09-20 08:17:56 UTC
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
  File "/usr/sbin/anaconda", line 281, in runVNC
  File "/usr/lib64/python2.7/site-packages/pyanaconda/vnc.py", line 198, in startServer
  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):

How reproducible:

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:

Expected results:
vnc server starts successfully

Additional info:
workaround_1: do not use "vnc" boot parameter
workaround_2: use "vnc ksdevice=eth0" boot parameters

Comment 1 Jan Stodola 2011-09-20 08:18:33 UTC
Created attachment 523972 [details]

Comment 2 Jan Stodola 2011-09-20 08:19:09 UTC
Created attachment 523973 [details]

Comment 4 Radek Vykydal 2011-10-07 12:47:32 UTC
This should be fixed in F17.

Comment 5 Jan Stodola 2012-06-29 12:14:46 UTC
Retested with anaconda-17.29, this issue is fixed, vnc installation finished without any traceback.

Closing this bug.

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