Description of problem: I was inputing initial password Version-Release number of selected component: anaconda-21.48.21-1 The following was filed automatically by anaconda: anaconda 21.48.21-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/devicelibs/lvm.py", line 519, in lvresize raise LVMError("lvresize failed for %s: %s" % (lv_name, msg)) File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 3294, in resize lvm.lvresize(self.vg.name, self._name, self.size) File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 448, in execute self.device.resize() 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 365, 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 191, 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: lvresize failed for lv00_Home: running lvm lvresize --force -L 120524m --config devices { preferred_names=["^/dev/mapper/", "^/dev/md/", "^/dev/sd"] } vg_wam-fc16/lv00_Home failed Additional info: 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 quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 product: Fedora" release: Cannot get release name. type: anaconda version: Fedora
Created attachment 994073 [details] File: anaconda-tb
Created attachment 994074 [details] File: anaconda.log
Created attachment 994075 [details] File: environ
Created attachment 994076 [details] File: lsblk_output
Created attachment 994077 [details] File: nmcli_dev_list
Created attachment 994078 [details] File: os_info
Created attachment 994079 [details] File: program.log
Created attachment 994080 [details] File: storage.log
Created attachment 994081 [details] File: syslog
Created attachment 994082 [details] File: ifcfg.log
Created attachment 994083 [details] File: packaging.log
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.