Red Hat Bugzilla – Bug 1029505
Duplicate kernel boot options after anaconda upgrade and creating new boot loader configuration on s390x
Last modified: 2016-05-10 16:42:47 EDT
Description of problem:
After anaconda upgrade on s390x and creating new boot loader configuration during the upgrade, some boot options are listed twice in kernel parameters section of zipl.conf (for example rd_NO_LUKS, KEYTABLE=...):
parameters="root=/dev/disk/by-path/ccw-0.0.3161-part3 rd_NO_LUKS LANG=en_US.UTF-8 rd_NO_LUKS LANG=en_US.UTF-8 rd_NO_MD KEYTABLE=us cio_ignore=all,!0.0.0009 SYSFONT=latarcyrheb-sun16 rd_DASD=0.0.3161 rd_NO_LVM rd_NO_DM dasd=0.0.3161 KEYTABLE=us rd_NO_MD crashkernel=auto rd_DASD=0.0.3161 SYSFONT=latarcyrheb-sun16 rd_NO_LVM rd_NO_DM"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install RHEL-6.4 on s390x
2. start graphical (vnc) installation of RHEL-6.5
3. select "Upgrade an Existing Installation" when asked
4. select "Create new boot loader configuration"
5. zipl configuration screen is displayed with "Kernel Parameters" field pre-filled like this:
"rd_NO_LUKS LANG=en_US.UTF-8 rn_NO_MD KEYTABLE=us cio_ignore=all,!0.0.0009 SYSFONT=latacryheb-sun16 rd_DASD=0.0.3161 rd_NO_LVM rd_NO_DM dasd=0.0.3161"
6. do not make any modification, click Next
7. finish the upgrade and reboot to installed system
8. check /etc/zipl.conf
Duplicate kernel parameters in zipl.conf
Each parameter is listed only once
* system boots correctly with duplicate boot options
* unable to reproduce on x86_64 (there is no zipl configuration screen)
Created attachment 822992 [details]
zipl.conf before upgrade
Created attachment 822993 [details]
zipl.conf after upgrade
Created attachment 822995 [details]
Created attachment 822996 [details]
This is a low priority with no customer case attached; additionally, it does not block installation or the ability to boot post-install, so I'm deferring to 6.7 planning.
Duplicate boot options are not present any more and any additional parameters added during the upgrade are added to the boot parameters on installed system.
Thanks, moving to VERIFIED
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.