Description of problem: Rescue image has following boot record in /etc/zipl.conf on s390x: [linux-/mnt/sysimage/boot/vmlinuz-0-rescue-4bedb0245dfb47caa852e3a257c9807b] image=/boot/vmlinuz-/mnt/sysimage/boot/vmlinuz-0-rescue-4bedb0245dfb47caa852e3a257c9807b ramdisk=/boot/initramfs-/mnt/sysimage/boot/vmlinuz-0-rescue-4bedb0245dfb47caa852e3a257c9807b.img parameters="rd.lvm.lv=fedora_rtt7/root rd.dasd=0.0.3627 cio_ignore=all,!condev rd.lvm.lv=fedora_rtt7/swap root=/dev/mapper/fedora_rtt7-root rd.dasd=0.0.3727 rd.znet=qeth,0.0.0a00,0.0.0a01,0.0.0a02,layer2=1,portno=0,portname=FOOBAR" Since the path "/boot/vmlinuz-/mnt/sysimage/boot/vmlinuz-0-rescue-4bedb0245dfb47caa852e3a257c9807b" doesn't exist, zipl fails to write boot configuration and the installation fails: 15:30:19,579 INFO program: Running... zipl 15:30:19,640 INFO program: Error: Image file '/boot/vmlinuz-/mnt/sysimage/boot/vmlinuz-0-rescue-4bedb0245dfb47caa852e3a257c9807b' in section 'linux-/mnt/sysimage/boot/vmlinuz-0-rescue-4bedb0245dfb47caa852e3a257c9807b': No such file or directory 15:30:19,640 INFO program: Using config file '/etc/zipl.conf' 15:30:19,640 DEBUG program: Return code: 1 Version-Release number of selected component (if applicable): anaconda-22.20.1-1 How reproducible: always on s390x Steps to Reproduce: 1. proceed through the installation using default values Actual results: Installing boot loader ================================================================================ ================================================================================ Question The following error occurred while installing the boot loader. The system will n ot be bootable. Would you like to ignore this and continue with installation? could not find IPL device Expected results: Boot loader successfully written, paths in /etc/zipl.conf are correct Additional info: Installation source: http://s390.koji.fedoraproject.org/test/20150312/s390x/os/
Created attachment 1001137 [details] dnf.log
Created attachment 1001138 [details] dnf.rpm.log
Created attachment 1001139 [details] hawkey.log
Created attachment 1001140 [details] packaging.log
Created attachment 1001141 [details] program.log
Created attachment 1001142 [details] storage.log
Created attachment 1001144 [details] zipl.conf
This will effect any non-grub bootloader, pretty much. Tested with extlinux, updates image at https://dshea.fedorapeople.org/1201429.img
(In reply to David Shea from comment #10) > effect Affect. Maybe both. English is hard.
Updates image works fine on s390x.
python-blivet-1.0.3-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/python-blivet-1.0.3-1.fc22
Package python-blivet-1.0.3-1.fc22, anaconda-22.20.4-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing python-blivet-1.0.3-1.fc22 anaconda-22.20.4-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-3846/anaconda-22.20.4-1.fc22,python-blivet-1.0.3-1.fc22 then log in and leave karma (feedback).
Package python-blivet-1.0.3-1.fc22, anaconda-22.20.4-1.fc22, libblockdev-0.7-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing python-blivet-1.0.3-1.fc22 anaconda-22.20.4-1.fc22 libblockdev-0.7-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-3846/libblockdev-0.7-1.fc22,anaconda-22.20.4-1.fc22,python-blivet-1.0.3-1.fc22 then log in and leave karma (feedback).
Retested with anaconda 22.20.8-1, this issue is fixed. Thanks, moving to VERIFIED.