Bug 1755899

Summary:	/usr/lib/kernel/install.d/20-zipl-kernel.install should not try to use /sbin/new-kernel-pkg in RHEL8
Product:	Red Hat Enterprise Linux 8	Reporter:	Vinzenz Feenstra [evilissimo] <vfeenstr>
Component:	s390utils	Assignee:	Dan Horák <dhorak>
Status:	CLOSED ERRATA	QA Contact:	Vilém Maršík <vmarsik>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	8.0	CC:	fmartine, jhlavac, mbocek, pravisha, pstodulk, rvr, vfeenstr, wchadwic
Target Milestone:	rc	Keywords:	Upgrades
Target Release:	8.0
Hardware:	s390x
OS:	Linux
Whiteboard:
Fixed In Version:	s390utils-2.6.0-22.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-05 22:25:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vinzenz Feenstra [evilissimo] 2019-09-26 12:30:16 UTC

Description of problem:
During the RPM upgrade transaction the /usr/lib/kernel/install.d/20-zipl-kernel.install script for installing new kernels is checking for the existence of /sbin/new-kernel-pkg which theoretically should not exist on RHEL8, however RHEL7 to RHEL8 inplace upgrades needs to provide the /sbin/new-kernel-pkg file to solve the upgrade transaction.
In this case the /usr/lib/kernel/install.d/20-zipl-kernel.install script won't use the builtin BLS entry generation and also causes the installation not to generate the initramfs with dracut as a result.

A solution for us would be if the script would take in consideration the existence of the /boot/loader or /boot/loader/entries directory which we would be able to create by running the zipl-switch-to-blscfg script before the upgrade transaction is executed.

Version-Release number of selected component (if applicable):
s390utils-base-2.6.0-21.el8.1.s390x (This is from 8.1 however the issue exists even before)

How reproducible:
Use the leapp upgrade tool to upgrade from RHEL7 to RHEL8

Steps to Reproduce:
1. leapp upgrade
2. reboot
3.

Actual results:
System is booted with a RHEL7 kernel, however a RHEL8 kernel is located in /boot without any suitable initramfs for it neither any bls config snippet is created.

Expected results:
The initramfs is generated, the bls entry for the new kernel is added to /boot/loader/entries

Additional info:

The leapp upgrade is currently only working with specific devel builds and the leapp team is happy to verify the fix.

Comment 6 Vinzenz Feenstra [evilissimo] 2019-09-27 12:54:06 UTC

I verified that the patch works as expected

Comment 7 Javier Martinez Canillas 2019-09-27 13:02:55 UTC

(In reply to Vinzenz Feenstra [evilissimo] from comment #6)
> I verified that the patch works as expected

Great, thanks a lot for testing it.

Comment 8 Vilém Maršík 2019-09-30 16:09:36 UTC

Patch confirmed as commit 63205a4dc4c400f75571869d87682c0cdb475830 in recent rhel-8.1.0 branch of s390utils.git . Reporter has verified the fix in Comment #6. Time has run out. Setting verified.

Comment 15 errata-xmlrpc 2019-11-05 22:25:39 UTC

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.

https://access.redhat.com/errata/RHBA-2019:3597