Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionVinzenz 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 6Vinzenz Feenstra [evilissimo]
2019-09-27 12:54:06 UTC
I verified that the patch works as expected
Comment 7Javier 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.
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.
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