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

BMH fails inspecting on ARM SNO due to incorrect boot order (HP)

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 3
    • Critical
    • None
    • None
    • None
    • Rejected
    • None
    • In Progress
    • Known Issue
    • Hide
      *Cause*: Certain models of ARM-based HPE servers such as ProLiant RL300 fail to boot from virtual media.
      *Consequence*: Virtual media based provisioning may fail on these machines.
      *Fix*: Currently, there is no known fix or workaround. Red Hat Engineering Teams are investigating this issue.
      *Result*: At the moment, it may not be possible to perform IPI deployments of ARM-based HPE ProLiant RL300 machines
      Show
      *Cause*: Certain models of ARM-based HPE servers such as ProLiant RL300 fail to boot from virtual media. *Consequence*: Virtual media based provisioning may fail on these machines. *Fix*: Currently, there is no known fix or workaround. Red Hat Engineering Teams are investigating this issue. *Result*: At the moment, it may not be possible to perform IPI deployments of ARM-based HPE ProLiant RL300 machines
    • None
    • None
    • None
    • None

      Description of problem:

          When we try to install an ARM SNO from x86 HUB using AI/ZTP flow, the node gets stuck inspecting. The node seems to boot into the old installation in the HDD and not the image provided by the infraEnv discovery ISO.
    On checking the bios config, it appears that virtual media (virtual cd-rom) has the lowest priority and does not seem to get updated. Manually updating this boot order and retrying install helps BMH finish inspecting.

      Version-Release number of selected component (if applicable):

          4.18.0

      How reproducible:

          It is reproducible on `cnfdg45` and `cnfdg37` machine everytime.

      Steps to Reproduce:

          1. Install ARM SNO from x86 hub using ZTP Assisted Installer flow
    2. BMH does not progress past inspecting
    3. Check for incorrect boot order in bios config
    4. Manually update the boot order and bump virtual media to first
    5. Retry install and node finishes inspecting.

      Actual results:

         Boot order remains unchanged and incorrect when BMH is inspecting

      Expected results:

         Boot order is automatically updated and node boots into correct ISO. Subsequently, BMH should finish inspecting and provisioning

      Additional info:

              janders@redhat.com Jacob Anders
              rh-ee-apalanis Abraham Miller
              None
              Abraham Miller, Steven Skeard
              Jad Haj Yahya Jad Haj Yahya
              None
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: