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

[4.14] vSphere ABI failed due to storage operator degraded

XMLWordPrintable

    • Important
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, installations on vSphere using the assisted installer could fail by preventing vSphere from initializing nodes correctly. With this update, assisted installations on vSphere successfully complete with all nodes initialized. (link:https://issues.redhat.com/browse/OCPBUGS-25718[*OCPBUGS-25718*])
      Show
      * Previously, installations on vSphere using the assisted installer could fail by preventing vSphere from initializing nodes correctly. With this update, assisted installations on vSphere successfully complete with all nodes initialized. (link: https://issues.redhat.com/browse/OCPBUGS-25718 [* OCPBUGS-25718 *])
    • Bug Fix
    • In Progress

      This is a clone of OCPBUGS-25718.
      The same issue was reported in OCP4.14.
      Could you check if it can be backported to 4.14?

      vSphere credentials are not set in the CSI Operator secret.
      As a result, the StorageClass is not created.

      As a workaround, ran the following steps:
      https://docs.openshift.com/container-platform/4.14/post_installation_configuration/installing-vsphere-post-installation-configuration.html

      —

      Description of problem:

      The degradation of the storage operator occurred because it couldn't locate the node by UUID. I noticed that the providerID was present for node 0, but it was blank for other nodes. A successful installation can be achieved on day 2 by executing step 4 after step 7 from this document: https://access.redhat.com/solutions/6677901. Additionally, if we provide credentials from the install-config, it's necessary to add a taint to the node using the uninitialized taint(oc adm taint node "$NODE" node.cloudprovider.kubernetes.io/uninitialized=true:NoSchedule) after the bootstrap completed.

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

      4.15

      How reproducible:

      100%

      Steps to Reproduce:

          1. Create an agent ISO image
    2. Boot the created ISO on vSphere VM   

      Actual results:

      Installation is failing due to storage operator unable to find the node by UUID.

      Expected results:

      Storage operator should be installed without any issue.

      Additional info:

      Slack discussion: https://redhat-internal.slack.com/archives/C02SPBZ4GPR/p1702893456002729

              beth.white Beth White
              rhn-support-mhans Manoj Hans
              Manoj Hans Manoj Hans
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: