Bump coreos-installer in 4.11 to add s390x Secure Execution support.
This bug has been reported fixed in a new RHCOS build and is ready for QE verification. To mark the bug verified, set the Verified field to Tested. This bug will automatically move to MODIFIED once the fix has landed in a new bootimage.
Tested with rhcos-411.86.202206301021-0-qemu.s390x.qcow2, the rpm is the correct version and rdcore has the --secex-mode flag: [core@cosa-devsh ~]$ rpm -qa | grep coreos-installer coreos-installer-0.15.0-2.rhaos4.11.el8.s390x coreos-installer-bootinfra-0.15.0-2.rhaos4.11.el8.s390x [core@cosa-devsh ~]$ /usr/lib/dracut/modules.d/50rdcore/rdcore zipl --help rdcore-zipl Runs zipl USAGE: rdcore zipl [OPTIONS] --boot-mount <BOOT_MOUNT> OPTIONS: --boot-mount <BOOT_MOUNT> Boot device containing BLS entries to use --secex-mode <SECEX_MODE> Zipl mode for Secure Execution [default: auto] [possible values: auto, enforce, disable] --rootfs <ROOTFS> Path to rootfs --hostkey <HOSTKEY> Path to hostkey --kargs <KARGS> Extra kargs -h, --help Print help information
The fix for this bug has landed in a bootimage bump, as tracked in bug 2093126 (now in status MODIFIED). Moving this bug to MODIFIED.
Moved to verified based on pre-verification.
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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/RHSA-2022:5069