Customer Contact Name: Yasuhiro Futakawa Description of Problem: IPI failed during iPXE boot because IRONIC_KERNEL_PARAMS does not contain coreos_kernel_params in inspector.ipxe file. To boot the coreos IPA, there are some coreos related kernel params need to be set, and they are passed to the bare metal servers through IRONIC_KERNEL_PARAMS. During iPXE boot, IRONIC_KERNEL_PARAMS is set in inspector.ipxe file which is rendered by the runhttpd script and currently coreos_kernel_params are not contained. This is because coreos_kernel_params will only be added into IRONIC_KERNEL_PARAMS if rootfs file exists, but the rootfs file is downloaded by the coreos-downloader which is currently started after the runhttpd script executed. Version-Release number of selected component: This issue was detected in the Pre-GA version. Red Hat OpenShift Container Platform Version Number: 4.10 Release Number: 4.10.0-0.nightly-2021-12-20-231053 Kubernetes Version: 1.22.1 Cri-o Version: 1.23.0 Related Component: NONE Related Middleware/Application: irmc Underlying RHCOS Release Number: 4.10 Underlying RHCOS Architecture: x86_64 Underlying RHCOS Kernel Version: 4.18.0 Drivers or hardware or architecture dependency: None How reproducible: Everytime Step to Reproduce: $ openshift-install --dir ~/clusterconfigs create manifests $ openshift-install --dir ~/clusterconfigs --log-level debug create cluster Actual Results: IPA can not be booted and IPI fails Expected Results: IPA can be booted correctly Summary of actions taken to resolve issue: Fujitsu sent PR: https://github.com/openshift/installer/pull/5541 Location of diagnostic data: None Hardware configuration: Model: RX2540 M4
This will need a backport of the revendoring in the installer to pick up the change.
Hi, PR5705 has been merged. Fujitsu tested OCP 4.10.13 which includes PR5705 and all fixes, and we confirmed that all of our features worked correctly. Best Regards, Yasuhiro Futakawa
Per the comment10 and discussed in the email, moving the bug to VERIFIED status.
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 (OpenShift Container Platform 4.10.13 bug fix 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-2022:1690