Description of problem: while setting the root password during install Version-Release number of selected component: anaconda-21.46-1 The following was filed automatically by anaconda: anaconda 21.46-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/formats/__init__.py", line 392, in create raise FormatCreateError("invalid device specification", self.device) File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 554, in execute options=self.device.formatArgs) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 354, in processActions action.execute() File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 357, in doIt self.devicetree.processActions() File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 216, in turnOnFilesystems storage.doIt() File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 179, in doInstall turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall) 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) FormatCreateError: ('invalid device specification', '/dev/sda1') Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-rawhide-x86-64 quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.16.0-0.rc3.git2.1.fc21.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: rawhide
Created attachment 914826 [details] File: anaconda-tb
Created attachment 914827 [details] File: anaconda.log
Created attachment 914828 [details] File: environ
Created attachment 914829 [details] File: lsblk_output
Created attachment 914830 [details] File: nmcli_dev_list
Created attachment 914831 [details] File: os_info
Created attachment 914832 [details] File: program.log
Created attachment 914833 [details] File: storage.log
Created attachment 914834 [details] File: syslog
Created attachment 914835 [details] File: ifcfg.log
Created attachment 914836 [details] File: packaging.log
Another user experienced a similar problem: Device type RAID > raid1, for /boot/efi, /boot, and /. Standard partition for swap. Click Begin install, crashes around the time it's creating disklabel on sdb. cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/isolinux/vmlinuz0 root=live:LABEL=Fedora-Live-Workstation-x86_64-r ro rd.live.image quiet rhgb hashmarkername: anaconda kernel: 3.16.0-0.rc3.git2.1.fc21.x86_64 other involved packages: python-libs-2.7.7-2.fc21.x86_64, python-blivet-0.60-1.fc21.noarch package: anaconda-core-21.46-2.fc21.x86_64 packaging.log: product: Fedora reason: FormatCreateError: ('invalid device specification', '/dev/sdb3') release: Fedora release 21 (Rawhide) version: rawhide
I think these are different bugs, I'm going to file mine separately. As reported in this bug, implies BIOS: device: /dev/sda1 self: non-existent biosboot Mine is UEFI and the failure was setting up mdadm member. device: /dev/sdb3 self: non-existent mdmember
I believe that this is very closely related to bz#1118150 and may be a duplicate. In both cases, the eventual exception is raised because the path for the partition does not exist, and for no other reason. In both cases, the problem seems to have nothing to do with the ordering of the actions, so must have something to do with their content.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.