Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-61350

Sideloading RHEL10 kernel on OCP 4.20 breaks networking

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Normal Normal
    • None
    • 4.20
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • x86_64
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem: When trying to sideload rhel-10.0-z-candidate kernel on top of OCP 4.20 deployment there is no network after reboot.

      Version-Release number of selected component (if applicable): 4.20.0-ec.5

      How reproducible: 100%

      Steps to Reproduce:

      1. Deploy OCP 4.20

      2. Try to sideload kernel

      3. Check iDRAC console

      Actual results:

      (OCR by Google Gemini, see screenshot for the original):

      Red Hat Enterprise Linux CoreOS 9.6.20250707-1 (Plow)
      Kernel 6.12.0-55.28.1.el9_0.x86_64+rt on an x86_64SSH host key: SHA256:xDNJKW5J9kTMb94KdF151gYfHOSDIc+rX8u32jfF321 (ECDSA)
      SSH host key: SHA256:OS2JbGpUWg6UrJimr+H1RRM+XaZoDt+fMts1cnDdul8 (RSA)
      SSH host key: SHA256:uAdKaiXzjwM7JouJg+uMTA2zAjYOLdgLpYvEDmacu0 (ED25519)
      Ignition: ran on 2025/08/13 15:31:07 UTC (at least 4 boots ago)
      Ignition: user-provided config was applied
      spree-04 login: [ 88.764633] bash[3126]: time="2025-08-14T15:14:32" level=info msg="Nodelp started with params: {retry:true primaryIP:
      referIP:6;false userManagedLB:false networkType:OveNKubernetes platform:}"
      [ 88.764705] bash[3126]: time="2025-08-14T15:14:32" level=info msg="Failed to read ip from file /run/nodeip-configuration/pri-
      mary-ip" error="open /run/nodeip-configuration/primary-ip: no such file or directory"
      [ 88.769240] bash[3126]: time="2025-08-14T15:14:32" level-error msg="Failed to find a suitable node IP"
      [ 90.770449] bash[3126]: time="2025-08-14T15:14:32" level-error msg="Failed to find a suitable node IP"
      [ OK ] Stopped Wait for chrony to synchronize system clock.
      [ OK ] Reached target System Time Synchronized.
      [ OK ] Started Daily rotation of log files.
      [ OK ] Started daily update of the root trust anchor for DNSSEC.
      [ OK ] Reached target Timer Units.
      Stopping ntp client/server...
      [ OK ] Stopped ntp client/server.
      [ OK ] Finished Tuned service from MTU image.
      [ 94.774174] bash[3126]: time="2025-08-14T15:14:92" level-error msg="Failed to find a suitable node IP"
      [ 102.781915] bash[3126]: time="2025-08-14T15:14:272" level-error msg="Failed to find a suitable node IP"  

      node is not reachable

      Expected results:

      Node is reachable after the reboot

      Additional info:

      This is part of the KPI effort for the look ahead kernel sideloading job

      Affected Platforms:

      Is it an

      1. internal RedHat testing failure

      If it is an internal RedHat testing failure:

      • I can reproduce the issue and give access to the cluster/node

      Please let me know if any other information is required

              bbennett@redhat.com Ben Bennett
              agurenko@redhat.com Alexander Gurenko
              None
              None
              Anurag Saxena Anurag Saxena
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: