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

RHCOS fails to reboot after disk install from agent based installer on s390x

XMLWordPrintable

    • None
    • Multi-Arch Sprint 263
    • 1
    • False
    • Hide

      None

      Show
      None
    • Hide
      Previously, the first reboot failed while running Agent-based Installer using FCP or NVME storage devices for multiple images on s390x hardware. With this release, this issue is resolved and the reboot completes. (
      ====
      With the support of multi-images on s390x the first reboot is failing while running Agend-based Installer using FCP or NVMe storage devices. With this release this issue is fixed. (OCPBUGS-44904)
      Show
      Previously, the first reboot failed while running Agent-based Installer using FCP or NVME storage devices for multiple images on s390x hardware. With this release, this issue is resolved and the reboot completes. ( ==== With the support of multi-images on s390x the first reboot is failing while running Agend-based Installer using FCP or NVMe storage devices. With this release this issue is fixed. ( OCPBUGS-44904 )
    • Bug Fix
    • Done

      This is a clone of issue OCPBUGS-42553. The following is the description of the original issue:
      —
      Context thread.

      Description of problem:

           Monitoring the 4.18 agent-based installer CI job for s390x (https://github.com/openshift/release/pull/50293) I discovered unexpected behavoir onces the installation triggers reboot into disk step for the 2nd and 3rd control plane nodes. (The first control plane node is rebooted last because it's also the bootstrap node). Instead of rebooting successully as expected, it fails to find the OSTree and drops to dracut, stalling the installation.

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

          OpenShift 4.18 on s390x only; discovered using agent installer

      How reproducible:

          Try to install OpenShift 4.18 using agent-based installer on s390x

      Steps to Reproduce:

          1. Boot nodes with XML (see attached)
    2. Wait for installation to get to reboot phase.

      Actual results:

          Control plane nodes fail to reboot.

      Expected results:

          Control plane nodes reboot and installation progresses.

      Additional info:

          See attached logs.

              kdo@redhat.com Kha Do
              openshift-crt-jira-prow OpenShift Prow Bot
              Amadeus Podvratnik Amadeus Podvratnik
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: