Description of problem: I was trying to reproduce bug 1036705. I removed all previous disk contents (I think it was LVM on mdraid 10). Then I created a new layout LVM on mdraid 10. I kept only a single / partition and downsized it (from the default size). It crashed on installation start. anaconda 20.25.11-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/devicelibs/lvm.py", line 437, in lvactivate raise LVMError("lvactivate failed for %s: %s" % (lv_name, msg)) File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 2682, in _setup lvm.lvactivate(self.vg.name, self._name) File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 716, in setup self._setup(orig=orig) File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 534, in execute self.device.setup(orig=True) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 234, in processActions action.execute() File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 308, in doIt self.devicetree.processActions() File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 167, in turnOnFilesystems storage.doIt() File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 142, in doInstall turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall) File "/usr/lib64/python2.7/threading.py", line 764, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 192, in run threading.Thread.run(self, *args, **kwargs) LVMError: lvactivate failed for root: running lvm lvchange -a y fedora/root failed Version-Release number of selected component (if applicable): anaconda 20.25.11-1 How reproducible: unknown
Created attachment 832006 [details] anaconda-tb
I could reproduce it as long as I deleted all contents and tried to create yet another LVM on mdraid 10. Once I tried to create default LVM (without mdraid) setup, installation worked ok. I'm unclear why anaconda tries to activate the older VG, when I chose to remove it and create a fresh new one. Maybe because the name of the old one and the name of the new one is the same? Is is possible that it tries to reuse it instead of re-creating it?
Is this reproducible in F21 or F22?
I tried to reproduce this bug with F22 Beta RC3, installation worked as expected, no bug encountered.