From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) Description of problem: Apparently my partition info in my kickstart script is crashing anaconda during a PXE install. (haven't tried it via a normal install yet) I used the following out of an anaconda-ks.conf file from a normal isntall: bootloader --location=mbr clearpart --linux --drives=sda part /boot --fstype "ext3" --size=100 --ondisk=sda part pv.2 --size=0 --grow --ondisk=sda volgroup VolGroup00 pv.2 logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=1000 --grow --maxsize=2000 logvol /var --fstype ext3 --name=LogVol02 --vgname=VolGroup00 --size=70080 logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=4096 Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Simply load the KS file above Actual Results: Anaconda crash/debug: The last bit is: File "/usr/src/build/475969-i386/install//usr/lib/anaconda/autopart.py", line 361, in fitSized requestSectors = long ((request.requestSize * 1024L * 1024L) / part.disk.dev.sector_size) - 1 TypeError: unsupported operand type(s) for *: 'NoneType' and 'long' Expected Results: Kept going.. Additional info:
Does this go away if you specify a size other than 0 for pv.2? :)
*mutter* as a matter of fact, it does. So why did it stick the 0 in anaconda- ks.conf then? Thanks for the help.
I got bit by this too.. it would be nice of anaconda-ks.cfg contained valid code. Chris