Bug 1192922 - Anaconda is dead on arrival with traceback in setupVirtio
Summary: Anaconda is dead on arrival with traceback in setupVirtio
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 22
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2015-02-16 08:53 UTC by Fabian Deutsch
Modified: 2015-02-16 09:03 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-02-16 09:03:44 UTC
Type: Bug

Attachments (Terms of Use)

Description Fabian Deutsch 2015-02-16 08:53:21 UTC
Description of problem:
As soon as I PXE start anaconda using todays pxe boot images and liveos squashfs (bug 1191713 is fixed), anaconda dies while starting with:
Traceback (most recent call last):
  File "/sbin/anaconda", line 807, in <module>
  File "/usr/lib64/python2.7/site-packages/pyanaconda/anaconda_log.py", line 241, in setupVirtio
    if not os.access(vport, os.W_OK):
TypeError: coercing to Unicode: need string or buffer, NoneType found

Version-Release number of selected component (if applicable):
anaconda from F22
# anaconda --version
anaconda 22.19-1

How reproducible:

Steps to Reproduce:
1. Use vmlinuz, initrd and squash from the F22 dir: https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-22&arch=x86_64
2. "PXE" boot using:
  qemu-system-x86_64 -enable-kvm \
	-vnc \
	-serial stdio \
	-smp 4 -m 2048 \
	-hda rootfs.qcow2 \
	-kernel vmlinuz \
	-initrd initrd.img \
	-device virtio-serial -chardev file,id=logfile,path=anaconda.log -device virtserialport,name=org.fedoraproject.anaconda.log.0,chardev=logfile \
	-append "console=ttyS0 inst.ks= inst.stage2= quiet cmdline inst.virtiolog " ; \

3. See anaconda crashing

Actual results:
anaconda crashes with a traceback when it starts

Expected results:
anaconda comes up and does the installation

Additional info:

Comment 1 Fabian Deutsch 2015-02-16 08:54:02 UTC
Maybe I missunderstood the inst.virtiolog argument. I understood it as a swicth to enable virtio logging, but maybe it should be seen as a argument which takes a value.

Comment 2 Fabian Deutsch 2015-02-16 09:03:44 UTC
Removing inst.virtiolog from the cmdline fixes this issue.

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