Red Hat Bugzilla – Bug 136526
unhandled python traceback in LVM configutation
Last modified: 2007-11-30 17:10:52 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Description of problem:
I received a traceback crash during an installation of FC3T3.
I'm doing kickstart installs, via pxeboot & a serial console.
My node is a Dell 2650, single 36M SCSI disk.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. boot the node using the following kernel command line:
Kernel command line: initrd=/install/fedora/3t3/initrd.img
console=ttyS0,9600 BOOT_IMAGE=/install/fedora/3t3/vmlinuz vnc
2. after prompting for keyboard type (separate bug), wait for the
crash to occur (everything else is specified in the kickstart file)
Actual Results: I got a traceback in a dialog box from anaconda.
Will be attached.
Created attachment 105535 [details]
traceback log from anaconda
Created attachment 105536 [details]
the kickstart config file used to generate the crash
Can you attach the full anacdump.txt? That will include /tmp/lvmout
which gives me additional debugging feedback fromthe lvm tools
I had been able to repeat this several time, but cannot do so now.
If/when this comes up again, where do I find anacdump.txt?
It'll be /tmp/anacdump.txt