The following was filed automatically by anaconda: anaconda 11.5.0.39 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/partitioning.py", line 1061, in growLVM portion = float(lv.req_size) / float(lv_total) File "/usr/lib/anaconda/storage/partitioning.py", line 193, in doAutoPartition growLVM(anaconda.id.storage) File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 128, in gotoNext self.moveStep() File "/usr/lib/anaconda/dispatch.py", line 227, in currentStep self.gotoNext() File "/usr/lib/anaconda/gui.py", line 1356, in setScreen (step, anaconda) = self.anaconda.dispatch.currentStep() File "/usr/lib/anaconda/gui.py", line 1519, in setup_window self.setScreen() File "/usr/lib/anaconda/gui.py", line 1529, in run self.setup_window(runres) File "/usr/lib/anaconda/gui.py", line 1276, in run self.icw.run (self.runres) File "/usr/bin/anaconda", line 968, in <module> anaconda.intf.run(anaconda) ZeroDivisionError: float division
Created attachment 337824 [details] Attached traceback automatically from anaconda.
part pv.2 --size=25000 volgroup VGVIRT --pesize=32768 pv.2 logvol /var/lib/libvirt/images --vgname=VGVIRT --fstype=btrfs --name LVVIRT --grow This ALSO happened when I added --size=1 --grow I moved to just hard coding --size without --grow and it at least installs...
Does using updates=http://clumens.fedorapeople.org/493656.img result in you getting an error saying that a size is required? The proper behavior here is that you get an error, since logvol requires a size to be specified, either through --size, --percent, or --useexisting.
Created attachment 337866 [details] Attached traceback automatically from anaconda.
The second problem (--size=1 --grow) should be fixed in anaconda-11.5.0.40-1.
What's the current status on this bug?
I've made a slightly better test to catch zero sized partitions and LVs, which I believe should fix this issue. Please try the next build of anaconda and let me know if this fixes your bug. Thanks.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping