Description of problem: This seems to happen if I am chrooted to /mnt/sysimage in a terminal when I restart the installer on the Live CD. Version-Release number of selected component: anaconda-18.29-1.fc18.x86_64 Additional info: libreport version: 2.0.17 cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8 kernel: 3.6.6-3.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.29 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicelibs/lvm.py", line 411, in lvdeactivate : raise LVMError("lvdeactivate failed for %s: %s" % (lv_name, msg)) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 2532, in _teardown : lvm.lvdeactivate(self.vg.name, self._name) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 758, in teardown : self._teardown(recursive=recursive) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 3113, in findExistingInstallations : device.teardown() : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 452, in reset : self.roots = findExistingInstallations(self.devicetree) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 139, in storageInitialize : storage.reset() : File "/usr/lib64/python2.7/threading.py", line 504, in run : self.__target(*self.__args, **self.__kwargs) : File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 91, in run : threading.Thread.run(self, *args, **kwargs) :LVMError: lvdeactivate failed for root: running lvm lvchange -a n --config devices { filter=["r|/loop5$|","r|/loop6$|","r|/loop7$|"] } fedora/root failed
Created attachment 646607 [details] File: anaconda-tb
Created attachment 646608 [details] File: environ
Created attachment 646609 [details] File: type
Created attachment 646610 [details] File: ifcfg.log
Created attachment 646611 [details] File: storage.log
Created attachment 646612 [details] File: version
Created attachment 646613 [details] File: program.log
Created attachment 646614 [details] File: executable
Created attachment 646615 [details] File: product
Created attachment 646616 [details] File: anaconda.log
Created attachment 646617 [details] File: hashmarkername
Created attachment 646618 [details] File: packaging.log
Created attachment 646619 [details] File: cmdline_file
Created attachment 646620 [details] File: release
Created attachment 646621 [details] File: messages
Created attachment 646622 [details] File: other involved packages
(In reply to comment #0) > Description of problem: > This seems to happen if I am chrooted to /mnt/sysimage in a terminal when I > restart the installer on the Live CD. Yeah -- don't do that. This is something that we plan to do our best to fix when things get quiet enough to have time for it, but even then we'll probably only be able to bow out a bit more gracefully.
An informative error message is already logged: [snippet from attached anaconda-tb] 15:48:41,242 INFO program: Running... lvm lvchange -a n --config devices { filter=["r|/loop5$|","r|/loop6$|","r|/loop7$|"] } fedora/root 15:48:41,330 ERR program: Logical volume fedora/root contains a filesystem in use. And for the details ... # lsof /dev/mapper/fedora-root
This is really quite far into "just don't do that" territory, especially given the quantity of more serious bugs we have to deal with. I'd be surprised if we ever do get around to finding time to deal with this.
Maybe you are smart enough to know enough to not do that, but the point of displaying an error message in an exception handler is to inform those multitudes who are not as smart as you are just how lacking in smarts they really are ... :-)
Here's a suprise, a bug gets reopened. In order to hit this bug, you first had to chroot into /mnt/sysimage and then run the live installer? That's a lot of manual steps, so some intelligence is assumed here. Anyway like I said, we've got a lot more serious stuff to do now, and we're likely to always have more important stuff to do. So I do not see us getting around to fixing this.