Hide Forgot
Version-Release number of selected component: anaconda-20.25.6-1 The following was filed automatically by anaconda: anaconda 20.25.6-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/formats/disklabel.py", line 294, in commit raise DiskLabelCommitError(msg) File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 1618, in _destroy self.disk.originalFormat.commit() File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 822, in destroy self._destroy() File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 318, in execute self.device.destroy() File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 242, in processActions action.execute() File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 310, in doIt self.devicetree.processActions() File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 169, 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 168, in run threading.Thread.run(self, *args, **kwargs) DiskLabelCommitError: Could not commit to disk /dev/mapper/mpatha, (py_ped_disk_commit) Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=LIVE rd.live.check quiet BOOT_IMAGE=vmlinuz executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.11.6-301.fc20.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 20-Beta
Created attachment 828358 [details] File: anaconda-tb
Created attachment 828359 [details] File: anaconda.log
Created attachment 828360 [details] File: environ
Created attachment 828361 [details] File: lsblk_output
Created attachment 828362 [details] File: nmcli_dev_list
Created attachment 828363 [details] File: os_info
Created attachment 828364 [details] File: program.log
Created attachment 828365 [details] File: storage.log
Created attachment 828366 [details] File: syslog
Created attachment 828367 [details] File: ifcfg.log
Created attachment 828368 [details] File: packaging.log
This doesn't seem to me like an anaconda bug. Maybe even not a python-blivet bug
Trouble probably starts here: 08:41:40,412 INFO program: Running... lvm pvs --unit=k --nosuffix --nameprefixes --rows --unquoted --noheadings -opv_uuid,pe_start,vg_name,vg_uuid,vg_size,vg_free,vg_extent_size,vg_extent_count,vg_free_count,pv_count --config global {locking_type=4} /dev/mapper/mpatha3 08:41:40,463 INFO program: No cache info in lvmetad cache for /dev/mapper/mpatha3. 08:41:40,464 INFO program: Failed to read physical volume "/dev/mapper/mpatha3" 08:41:40,464 DEBUG program: Return code: 5
It looks like this was a live install attempt, maybe something in the desktop environment has it open? If you can reproduce this you could try running lsof on mpatha3 and see if it shows anything. Also the output of mount may be helpful.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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.