Description of problem: setting up instal env soas anaconda 21.48.13-1 (reclaimed disk) Version-Release number of selected component: anaconda-core-21.48.13-1.fc21.x86_64 The following was filed automatically by anaconda: anaconda 21.48.13-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/devicelibs/lvm.py", line 508, in lvremove raise LVMError("lvremove failed for %s: %s" % (lv_name, msg)) File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 3140, in _destroy lvm.lvremove(self.vg.name, self._name) File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 964, in destroy self._destroy() File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 336, in execute self.device.destroy() File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 361, in processActions action.execute(callbacks) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 364, in doIt self.devicetree.processActions(callbacks) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 216, in turnOnFilesystems storage.doIt(callbacks) File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 190, in doInstall turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall, callbacks=callbacks_reg) File "/usr/lib64/python2.7/threading.py", line 766, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 227, in run threading.Thread.run(self, *args, **kwargs) LVMError: lvremove failed for home: running lvm lvremove --config devices { preferred_names=["^/dev/mapper/", "^/dev/md/", "^/dev/sd"] filter=["r|/sda1$|","r|/sda2$|","r|/sda3$|","r|/sda$|","r|/sdc1$|","r|/sdc2$|","r|/sdc$|"] } fedora/home failed Additional info: cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-SoaS-x86_64-21_Beta- rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.17.1-302.fc21.x86_64 other involved packages: python-blivet-0.61.8-1.fc21.noarch, python-libs-2.7.8-4.1.fc21.x86_64 product: Fedora" release: Fedora release 21 (Twenty One) type: anaconda version: Fedora
Created attachment 951770 [details] File: anaconda-tb
Created attachment 951771 [details] File: anaconda.log
Created attachment 951772 [details] File: environ
Created attachment 951773 [details] File: journalctl
Created attachment 951774 [details] File: lsblk_output
Created attachment 951775 [details] File: nmcli_dev_list
Created attachment 951776 [details] File: os_info
Created attachment 951777 [details] File: program.log
Created attachment 951778 [details] File: storage.log
Created attachment 951779 [details] File: ifcfg.log
Another user experienced a similar problem: Installing Fedora 21 from Fedora-Server-netinst-x86_64-21.iso. I had selected to install PC Workstation. This happen after I started installation and was changing the root password. addons: com_redhat_kdump cmdline: /usr/bin/python /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-21-x86_64 rd.live.check quiet hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 package: anaconda-21.48.21-1 product: Fedora" reason: LVMError: lvremove failed for home: running lvm lvremove --config devices { preferred_names=["^/dev/mapper/", "^/dev/md/", "^/dev/sd"] } fedora/home failed release: Cannot get release name. version: Fedora
It looks like this is triggered by the presence of multiple VGs with the same name and an overlapping subset of LV names. The solution is to raise a fatal exception when this case is detected so the user can resolve the problem outside the installer.
As of python-blivet-0.76-1 you should get a fatal exception if your system contains duplicate VGs (multiple VGs with the same name). Due to limitations in the lvm tools, this situation must be resolved before installing Fedora. I am currently working on making anaconda display an error message with a suggestion for how to resolve the issue.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.