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.
Bug 1902273 - s390utils 2.15.1-2 rebase broken BLS entries (and thus osbuild)
Summary: s390utils 2.15.1-2 rebase broken BLS entries (and thus osbuild)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: s390utils
Version: 8.4
Hardware: s390x
OS: Unspecified
unspecified
urgent
Target Milestone: rc
: 8.0
Assignee: Dan Horák
QA Contact: Vilém Maršík
URL:
Whiteboard:
: 1903691 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-27 14:39 UTC by Christian Kellner
Modified: 2021-05-18 14:55 UTC (History)
7 users (show)

Fixed In Version: s390utils-2.15.1-3.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-18 14:55:06 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
[PATCH] - add again the 00-zipl-prepare.install script that got dropped (#1902273) (3.65 KB, patch)
2020-11-27 15:26 UTC, Javier Martinez Canillas 		no flags Details | Diff
View All

Description Christian Kellner 2020-11-27 14:39:43 UTC 
The rebase of s390utils (https://src.osci.redhat.com/rpms/s390utils/c/542d595d5c36d5f73023272294bdba52cf99053b?branch=rhel-8.4.0) drastically changed the contents of the BLS entry in /boot/loader/entries/ which drastically changed the contents, including the paths to the kernel image. The latter breaks osbuild since we it uses the path from the BLS entry to determine the location of the kernel. 

It looks like the entries are not created by "90-loaderentry.install" instead of "20-zipl-kernel.install", which could be due to the fact that "00-zipl-prepare.install" was removed.
Comment 1 Javier Martinez Canillas 2020-11-27 15:26:46 UTC 
Created attachment 1734152 [details]
[PATCH] - add again the 00-zipl-prepare.install script that got dropped (#1902273)

Attaching a patch to fix this. The problem was that the 00-zipl-prepare.install script got dropped in the rebase and this is needed to prevent the systemd-boot kernel-install plugin to install their BLS snippets.
Comment 3 Javier Martinez Canillas 2020-11-27 15:55:54 UTC 
One clarification from the bug report is that this issue is not specific to osbuild, it should be present in any RHEL8.4 s390x image. In fact, this seems to be a duplicate of #1901874.
Comment 4 Javier Martinez Canillas 2020-11-27 16:00:49 UTC 
(In reply to Javier Martinez Canillas from comment #3)
> One clarification from the bug report is that this issue is not specific to
> osbuild, it should be present in any RHEL8.4 s390x image. In fact, this
> seems to be a duplicate of #1901874.

I meant Bug #1901874 here (without "Bug" a link is not created).
Comment 5 Buvanesh Kumar 2020-12-01 14:46:23 UTC 
This is affecting RHEL-8.4 production nightly.
Task: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=33398066
Error: Image file '/run/osbuild/output/osbuild-mnt-44j9mpad/ffffffffffffffffffffffffffffffff/4.18.0-256.el8.s390x/linux': No such file or directory
Comment 11 smitterl 2020-12-09 12:42:57 UTC 
*** Bug 1903691 has been marked as a duplicate of this bug. ***
Comment 16 Vilém Maršík 2021-02-19 22:15:24 UTC 
I think this looks fixed.
Old version:
# rpm -q s390utils-base
s390utils-base-2.15.1-2.el8.s390x
# rpm -i kernel-4.18.0-286.el8.s390x.rpm kernel-core-4.18.0-286.el8.s390x.rpm kernel-modules-4.18.0-286.el8.s390x.rpm
dracut: Disabling early microcode, because kernel does not support it. CONFIG_MICROCODE_[AMD|INTEL]!=y
Error: Config file '/etc/zipl.conf': Line 7: no such section 'Red Hat Enterprise Linux (4.18.0-286.el8.s390x) 8.4 (Ootpa)'
warning: %posttrans(kernel-core-4.18.0-286.el8.s390x) scriptlet failed, exit status 1
# find /boot/ | grep initr
/boot/initramfs-4.18.0-240.el8.s390x.img
/boot/initramfs-0-rescue-8a75c72f6c574233a54a3e5bf65201cc.img
/boot/initramfs-4.18.0-240.el8.s390xkdump.img
/boot/initramfs-4.18.0-286.el8.s390xkdump.img
/boot/8a75c72f6c574233a54a3e5bf65201cc/4.18.0-286.el8.s390x/initrd
/boot/8a75c72f6c574233a54a3e5bf65201cc/0-rescue/initrd

New version:
# rpm -q s390utils-base
s390utils-base-2.15.1-4.el8.s390x
# rpm -i kernel-4.18.0-286.el8.s390x.rpm kernel-core-4.18.0-286.el8.s390x.rpm kernel-modules-4.18.0-286.el8.s390x.rpm
# find /boot/ | grep initr
/boot/initramfs-4.18.0-240.el8.s390x.img
/boot/initramfs-0-rescue-8a75c72f6c574233a54a3e5bf65201cc.img
/boot/initramfs-4.18.0-240.el8.s390xkdump.img
/boot/initramfs-4.18.0-286.el8.s390x.img
Comment 18 errata-xmlrpc 2021-05-18 14:55:06 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 (s390utils bug fix and enhancement update), 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-2021:1617
Note You need to log in before you can comment on or make changes to this bug.