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

SNO installation failure on IBM Z LPAR

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • 4.19.0
    • Multi-Arch
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      Single node installation using bootstrap in place method fails on LPAR see below:
      
      bootstrap installed successfully 
      After bootstrap reboot, master boot failed because it didn't get the required config and it entered in to the emergency cell.
      As part of SNO bring up first boot will happen on ephemeral disk. After bootstrap reboot it didn't get the required config to load the OS

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

          

      How reproducible:

      Launch installation on LPAR using below install-config:
      controlPlane:
        hyperthreading: Enabled
        name: master
        replicas: 1
        architecture: s390x
      metadata:
        name: nvme
      networking:
        clusterNetwork:
        - cidr: 10.128.0.0/14
          hostPrefix: 23
        machineNetwork:
        - cidr: 172.23.0.0/16
        networkType: OVNKubernetes
        serviceNetwork:
        - 172.30.0.0/16
      platform:
        none: {}
      bootstrapInPlace:
        installationDisk: /dev/nvme0n1    

      Steps to Reproduce:

         

      Actual results:

      Installation failed.

      Expected results:

      Installation should continue after bootstrap reboot. 

      Additional info:

          

              rphaneen Phaneendra Ravuri
              madeelrh Muhammad Adeel
              None
              Amrut purandare (Inactive), Chidanand Harlapur, Dominik Werle
              None
              None
              IBM Confidential Group, Red Hat Employee
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: