-
Bug
-
Resolution: Done
-
Blocker
-
ACM 2.14.0
-
None
-
Quality / Stability / Reliability
-
2
-
False
-
-
False
-
-
-
Workload Mgmt Train 28 - 2, Workload Mgmt Train 29 - 1
-
Important
-
None
Description of problem:
In below example we select 14 Clusters and some have issues but there are many that work
It seems we only get latest error....
kind: GitOpsCluster metadata: creationTimestamp: '2025-03-12T06:08:12Z' generation: 1 managedFields: - apiVersion: apps.open-cluster-management.io/v1beta1 fieldsType: FieldsV1 fieldsV1: f:spec: .: {} f:argoServer: .: {} f:argoNamespace: {} f:placementRef: {} manager: unknown operation: Update time: '2025-03-12T06:08:12Z' - apiVersion: apps.open-cluster-management.io/v1beta1 fieldsType: FieldsV1 fieldsV1: f:status: .: {} f:lastUpdateTime: {} f:message: {} f:phase: {} manager: gitopscluster operation: Update subresource: status time: '2025-04-02T15:35:26Z' name: august-argo namespace: openshift-gitops resourceVersion: '187501959' uid: a2d10da2-1ce4-4dd2-a3c5-d68560c38a1d spec: argoServer: argoNamespace: openshift-gitops placementRef: apiVersion: cluster.open-cluster-management.io/v1beta1 kind: Placement name: august-argo-placement status: lastUpdateTime: '2025-04-02T15:35:26Z' message: 'no client configs found for managed cluster: ushift20-munich-lab' phase: failed
I expect to see list of clusters added and list of clusters failed
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
- ...