The following was filed automatically by anaconda: anaconda 13.27 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/devicelibs/lvm.py", line 418, in lvdeactivate raise LVMError("lvdeactivate failed for %s: %s" % (lv_name, msg)) File "/usr/lib/anaconda/storage/devices.py", line 2286, in teardown lvm.lvdeactivate(self.vg.name, self._name) File "/usr/lib/anaconda/storage/__init__.py", line 2009, in umountFilesystems device.teardown() File "/usr/lib/anaconda/storage/__init__.py", line 1139, in umountFilesystems self.fsset.umountFilesystems(ignoreErrors=ignoreErrors, swapoff=swapoff) File "/usr/lib/anaconda/livecd.py", line 174, in doPreInstall anaconda.storage.umountFilesystems(swapoff = False) File "/usr/lib/anaconda/backend.py", line 294, in doPreInstall anaconda.backend.doPreInstall(anaconda) File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1313, in nextClicked self.anaconda.dispatch.gotoNext() File "/usr/lib/anaconda/iw/progress_gui.py", line 79, in renderCallback self.intf.icw.nextClicked() File "/usr/lib/anaconda/gui.py", line 1334, in handleRenderCallback self.currentWindow.renderCallback() LVMError: lvdeactivate failed for lv_swap: LV VolGroup/lv_swap in use: not deactivating
Created attachment 395896 [details] Attached traceback automatically from anaconda.
*** Bug 567976 has been marked as a duplicate of this bug. ***
Created attachment 396183 [details] Attached traceback automatically from anaconda.
I hit this attempting to do an install of a F13 alpha RC3 live build - anaconda 13.31. This is with a 'delete existing Linux partitions' install into a KVM (using virt-manager). The disk image had been used for a previous failed attempt at installing, I don't know offhand what state it was in. Will re-test with a clean disk image and see what happens.
Same failure with a brand new, never-used-for-anything disk image, doing a next-next-next install. Looks like a blocker to me...
I notice this in dmesg: Adding 983032k swap on /dev/mapper/vg testbed-lv_swap. Priority:-1 extents:1 across:983032k is the system *using* the swap area that was created by anaconda and hence causing anaconda to barf?
anaconda-13.32-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/anaconda-13.32-1.fc13
anaconda-13.32-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update anaconda'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F13/FEDORA-2010-2985
Using the latest DVD installer image (as of an hour ago) I can install successfully.
Yes, this is fixed in RC4. Confirmed here.
anaconda-13.32-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 562335 has been marked as a duplicate of this bug. ***
*** Bug 566645 has been marked as a duplicate of this bug. ***