Description of problem: If a UOCR validation fails for any reason (e.g., non-existed spoke name), it will not show any status in UOCR as if the cr is still disabled. Version-Release number of selected component (if applicable): 4.10 How reproducible: 100% Steps to Reproduce: 1. Deploy upgrade operator 2. Create a UOCR with non-exist spokes 3. Enable UOCR Actual results: No status from UOCR at all. apiVersion: ran.openshift.io/v1alpha1 kind: ClusterGroupUpgrade metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"ran.openshift.io/v1alpha1","kind":"ClusterGroupUpgrade","metadata":{"annotations":{},"name":"basicplatform","namespace":"default"},"spec":{"clusters":["helix21-0","helix21-1","helix21-2","helix21-3"],"enable":false,"managedPolicies":["cluster-version-policy"],"remediationStrategy":{"maxConcurrency":4}}} creationTimestamp: "2022-01-14T18:37:27Z" generation: 3 name: basicplatform namespace: default resourceVersion: "2128564" uid: d6f3edfa-c809-41f5-8cc4-3b2255c718a7 spec: clusters: - helix21-0 - helix21-1 - helix21-2 enable: true managedPolicies: - cluster-version-policy remediationStrategy: maxConcurrency: 4 timeout: 240 Expected results: UOCR should indicate something went wrong Additional info: Workaround is to find relevant error in uocr pod logs.
Addressed by https://github.com/openshift-kni/cluster-group-upgrades-operator/pull/314
status: conditions: - lastTransitionTime: "2022-10-28T22:55:00Z" message: 'Unable to select clusters: cluster ltest-sno-1 is not a ManagedCluster' reason: NotFound status: "False" type: ClustersSelected status: {} Verified with 4.12 TALM.