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

Pending CSR in Hypershift PowerVS cluster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.17.z
    • 4.17.0
    • HyperShift
    • Important
    • None
    • False
    • Hide

      None

      Show
      None
    • Hide
      Previously, the provider ID for IBMPowerVSMachine's object did not populate properly due to an improper retrieval of the IBM Cloud Workspace ID. As a result, certificate signing requests (CSR) were pending in the hosted cluster. With this release, the provider ID successfully populates and the issue is resolved. (link:https://issues.redhat.com/browse/OCPBUGS-44880[*OCPBUGS-44880*])
      -------
      *Cause*: Provider ID for IBMPowerVSMachine's object is not populated properly, due to improper retrieval of IBM Cloud Workspace ID.
      *Consequence*: Pending CSRs in hosted cluster.
      *Fix*: Populate the provider ID properly for IBMPowerVSMachine.
      *Result*: No pending CSRs and all COs are moved to available state.
      Show
      Previously, the provider ID for IBMPowerVSMachine's object did not populate properly due to an improper retrieval of the IBM Cloud Workspace ID. As a result, certificate signing requests (CSR) were pending in the hosted cluster. With this release, the provider ID successfully populates and the issue is resolved. (link: https://issues.redhat.com/browse/OCPBUGS-44880 [* OCPBUGS-44880 *]) ------- *Cause*: Provider ID for IBMPowerVSMachine's object is not populated properly, due to improper retrieval of IBM Cloud Workspace ID. *Consequence*: Pending CSRs in hosted cluster. *Fix*: Populate the provider ID properly for IBMPowerVSMachine. *Result*: No pending CSRs and all COs are moved to available state.
    • Bug Fix
    • In Progress

      Description of problem:

          Pending CSR in PowerVS Hypershift cluster causes monitoring CO to not become available. Upon investigation providerID format set by CAPI is improper.

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

      4.17.0

      How reproducible:

         100%

      Steps to Reproduce:

          1.Create a cluster with hypershift on powervs with 4.17 release image.
    2.
    3.

      Actual results:

      Pending CSRs and monitoring CO in unavailable state

      Expected results:

      No pending CSRs and all CO should be available

      Additional info:

              dravicha Dharaneeshwaran Ravichandran
              dravicha Dharaneeshwaran Ravichandran
              Liangquan Li Liangquan Li
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: