Bug 2041765 - [FJ OCP4.10 Bug]: IRONIC_KERNEL_PARAMS does not contain coreos_kernel_params during iPXE boot
Summary: [FJ OCP4.10 Bug]: IRONIC_KERNEL_PARAMS does not contain coreos_kernel_params ...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.z
Assignee: Jacob Anders
QA Contact: Amit Ugol
Depends On: 2047925
Blocks: 1920358
TreeView+ depends on / blocked
Reported: 2022-01-18 09:01 UTC by Fujitsu container team
Modified: 2022-05-11 10:32 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2047925 (view as bug list)
Last Closed: 2022-05-11 10:31:46 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift baremetal-operator pull 200 0 None Merged Bug 2041765: irmc: change BootInterface to ipxe 2022-01-27 00:51:14 UTC
Github openshift installer pull 5541 0 None Merged Bug 2041765: Adjust the startup order of httpd container 2022-01-28 09:58:41 UTC
Github openshift installer pull 5705 0 None open [release-4.10] Bug 2041765: Update BMO vendor 2022-03-15 08:26:12 UTC
Red Hat Product Errata RHBA-2022:1690 0 None None None 2022-05-11 10:32:20 UTC

Description Fujitsu container team 2022-01-18 09:01:31 UTC
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:


How reproducible:


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:


Hardware configuration:

  Model: RX2540 M4

Comment 5 Zane Bitter 2022-01-28 21:10:54 UTC
This will need a backport of the revendoring in the installer to pick up the change.

Comment 10 Fujitsu container team 2022-05-09 01:17:12 UTC

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

Comment 11 Wei Sun 2022-05-10 10:40:03 UTC
Per the comment10 and discussed in the email, moving the bug to VERIFIED status.

Comment 13 errata-xmlrpc 2022-05-11 10:31:46 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 (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.


Note You need to log in before you can comment on or make changes to this bug.