Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-2406

"Condition not found in the CVO" reported for successfully deployed spoke on hypershift

XMLWordPrintable

    • False
    • None
    • False
    • Yes
    • Moderate

      Description of problem:

      {}Multiple errors shown while cluster is creating and still shown when the process successfully finished

      tjelinek@redhat.com first investigation:

      we have a hypershift cluster installed successfully with agent workers. The conditions on it show some strange things though, namely:

      • lastTransitionTime: "2022-12-14T09:15:38Z"
        message: Condition not found in the CVO.
        observedGeneration: 2
        reason: StatusUnknown
        status: Unknown
        type: ClusterVersionAvailable
      • lastTransitionTime: "2022-12-14T09:15:38Z"
        message: Condition not found in the CVO.
        observedGeneration: 2
        reason: StatusUnknown
        status: Unknown
        type: ClusterVersionProgressing
      • lastTransitionTime: "2022-12-14T09:15:38Z"
        message: Condition not found in the CVO.
        observedGeneration: 2
        reason: StatusUnknown
        status: Unknown
        type: ClusterVersionReleaseAccepted
         
        this results in us showing this errors in UI

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

        hypershift  4.12.0-0.nightly-2022-12-09-063749

        MCE 2.2.0-DOWNANDBACK-2022-12-12-02-00-28

        How reproducible:

        Steps to Reproduce:

      1. Create hypershift cluster (3 masters, virtualmedia). Open its console
      2. Create infraenv
      3. Create a spoke cluster

      Actual results:

      Multiple errors (see above)

      Expected results:

      No errors reported when the cluster is succesfuly reported

      Additional info:

            rokejungrh Roke Jung
            lshilin Lubov Shilin
            David Huynh David Huynh
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: