Bug 2047925 - [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.11.0
Assignee: Tomas Sedovic
QA Contact: Eldar Weiss
Depends On:
Blocks: 1920358 2041765
TreeView+ depends on / blocked
Reported: 2022-01-28 21:08 UTC by Zane Bitter
Modified: 2022-08-10 10:45 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2041765
Last Closed: 2022-08-10 10:45:08 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift installer pull 5588 0 None open Bug 2047925: Update BMO vendor 2022-01-28 21:13:33 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:45:36 UTC

Description Zane Bitter 2022-01-28 21:08:54 UTC
+++ This bug was initially created as a clone of Bug #2041765 +++

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 3 Fujitsu container team 2022-02-17 01:02:14 UTC

Fujitsu confirmed that IPI worked correctly with the latest nightly which contains PR5588.

Best Regards,
Yasuhiro Futakawa

Comment 4 Eldar Weiss 2022-03-16 16:22:13 UTC
Fix succesfully verified.
Version: 4.11.0-0.nightly-2022-03-15-223029

[kni@provisionhost-0-0 ocp-edge-auto]$ oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.11.0-0.nightly-2022-03-15-223029   True        False         12m     Cluster version is 4.11.0-0.nightly-2022-03-15-223029
[kni@provisionhost-0-0 ocp-edge-auto]$ oc --dir ~/clusterconfigs create manifests
[kni@provisionhost-0-0 ocp-edge-auto]$  ~/openshift-baremetal-install --dir ~/clusterconfigs create manifests
INFO Manifests created in: /home/kni/clusterconfigs/manifests and /home/kni/clusterconfigs/openshift 

Actual results:
Successful deployment.
No failure in IPI

Comment 6 errata-xmlrpc 2022-08-10 10:45:08 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 (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.


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