Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1201429 - Incorrect paths for rescue image in /etc/zipl.conf
Summary: Incorrect paths for rescue image in /etc/zipl.conf
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 22
Hardware: s390x
OS: Linux
high
high
Target Milestone: ---
Assignee: David Shea
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ZedoraTracker
TreeView+ depends on / blocked
 
Reported: 2015-03-12 17:01 UTC by Jan Stodola
Modified: 2015-04-15 12:24 UTC (History)
4 users (show)

Fixed In Version: anaconda-22.20.4-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-15 12:24:51 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
dnf.log (150.00 KB, text/plain)
2015-03-12 17:02 UTC, Jan Stodola 		no flags Details
dnf.rpm.log (43.47 KB, text/plain)
2015-03-12 17:02 UTC, Jan Stodola 		no flags Details
hawkey.log (1.02 KB, text/plain)
2015-03-12 17:02 UTC, Jan Stodola 		no flags Details
packaging.log (1.94 KB, text/plain)
2015-03-12 17:02 UTC, Jan Stodola 		no flags Details
program.log (41.47 KB, text/plain)
2015-03-12 17:02 UTC, Jan Stodola 		no flags Details
storage.log (166.69 KB, text/plain)
2015-03-12 17:02 UTC, Jan Stodola 		no flags Details
zipl.conf (921 bytes, text/plain)
2015-03-12 17:02 UTC, Jan Stodola 		no flags Details
View All

Description Jan Stodola 2015-03-12 17:01:40 UTC 
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/
Comment 2 Jan Stodola 2015-03-12 17:02:33 UTC 
Created attachment 1001137 [details]
dnf.log
Comment 3 Jan Stodola 2015-03-12 17:02:35 UTC 
Created attachment 1001138 [details]
dnf.rpm.log
Comment 4 Jan Stodola 2015-03-12 17:02:37 UTC 
Created attachment 1001139 [details]
hawkey.log
Comment 5 Jan Stodola 2015-03-12 17:02:38 UTC 
Created attachment 1001140 [details]
packaging.log
Comment 6 Jan Stodola 2015-03-12 17:02:41 UTC 
Created attachment 1001141 [details]
program.log
Comment 7 Jan Stodola 2015-03-12 17:02:43 UTC 
Created attachment 1001142 [details]
storage.log
Comment 9 Jan Stodola 2015-03-12 17:02:47 UTC 
Created attachment 1001144 [details]
zipl.conf
Comment 10 David Shea 2015-03-12 18:03:38 UTC 
This will effect any non-grub bootloader, pretty much. Tested with extlinux, updates image at https://dshea.fedorapeople.org/1201429.img
Comment 11 David Shea 2015-03-12 18:16:52 UTC 
(In reply to David Shea from comment #10)
> effect

Affect. Maybe both. English is hard.
Comment 12 Jan Stodola 2015-03-13 08:26:22 UTC 
Updates image works fine on s390x.
Comment 13 Fedora Update System 2015-03-13 18:33:15 UTC 
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
Comment 14 Fedora Update System 2015-03-14 09:14:06 UTC 
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).
Comment 15 Fedora Update System 2015-03-18 10:35:51 UTC 
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).
Comment 16 Jan Stodola 2015-04-15 12:24:18 UTC 
Retested with anaconda 22.20.8-1, this issue is fixed.

Thanks, moving to VERIFIED.
Note You need to log in before you can comment on or make changes to this bug.