RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

In the fix of the bug#1755899, there was introduced a change in the decision logic of the /usr/lib/kernel/install.d/20-zipl-kernel.install script. Specifically, whether the Boot Loader Specification (BLS) is used. Instead of just checking the existence of the /sbin/new-kernel-pkg file, the existence of the /boot/loader/entries directory is also checked.

More thorough testing revealed that the fix covers only the case when a new kernel is added. However, the remaining cases should also be covered. That means the case when a rescue kernel is added and the case when some kernel is removed.


Version-Release number of selected component:
s390utils-base-2.6.0-22.el8


Actual results:
When a rescue kernel is added or when some kernel is removed, the 52-zipl-rescue.install and 20-zipl-kernel.install scripts only check the existence of the /sbin/new-kernel-pkg file.


Expected results:
When a rescue kernel is added or when some kernel is removed, the 52-zipl-rescue.install and 20-zipl-kernel.install scripts check the existence of the /sbin/new-kernel-pkg file and the existence of the /boot/loader/entries directory.


Additional info:
A new fix already exists (bug#1755899 => attachment#1627629 [details]). It just needs to be rebased.

Is SanityOnly testing enough here?

Yes, it is. Later we can get feedback also from the in-place upgrade team, the original issue was their.

The fix looks applied to /usr/lib/kernel/install.d/20-zipl-kernel.install and /usr/lib/kernel/install.d/52-zipl-rescue.install in 8.2 Beta on s390x. Setting verified/sanityonly.

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-2020:1826