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

Pending CSR in Hypershift PowerVS cluster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • 4.18.0
    • 4.18.0
    • HyperShift
    • None
    • Important
    • None
    • Proposed
    • False
    • Hide

      None

      Show
      None
    • Hide
      *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
      *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.18.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
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: