-
Bug
-
Resolution: Done
-
Major
-
ACM 2.8.0
-
False
-
None
-
False
-
No
-
+
-
-
-
Important
Description of problem:
On a RDR setup, While trying to deploy application set based application from ACM console, UI throws an error in placement page saying "ClusterSets failed to load. Check the GitOpsCluster and Placement YAML for status errors."
Version-Release number of selected component (if applicable):
2.8.0
How reproducible:
always
Steps to Reproduce:
- Go to All Clusters -> Applications -> Create application -> Application set
- Provide details required from steps 1 to 3 and reach step 4 "Placement" page
- Observe the error "ClusterSets failed to load. Check the GitOpsCluster and Placement YAML for status errors."
Actual results:
UI throws error "ClusterSets failed to load. Check the GitOpsCluster and Placement YAML for status errors." and does not allow to select any clusterset.
Expected results:
There should not be any error while creating application set based applications
Additional info:
ManagedClusterSets:
$ oc get managedclustersets
NAME EMPTY AGE
default False 3d5h
global False 3d5h
submariner False 3d4h
GitOpsCluster and Placement YAML output from the cluster:
$ oc get gitopsclusters -n openshift-gitops -o yaml
apiVersion: v1
items:
- apiVersion: apps.open-cluster-management.io/v1beta1
kind: GitOpsCluster
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"apps.open-cluster-management.io/v1beta1","kind":"GitOpsCluster","metadata":{"annotations":{},"name":"gitops-cluster-sample","namespace":"openshift-gitops"},"spec":{"argoServer":{"argoNamespace":"openshift-gitops","cluster":"local-cluster"},"placementRef":{"apiVersion":"cluster.open-cluster-management.io/v1beta1","kind":"Placement","name":"all-openshift-clusters"}}}
creationTimestamp: "2023-06-19T07:22:16Z"
generation: 1
name: gitops-cluster-sample
namespace: openshift-gitops
resourceVersion: "3702199"
uid: 88717f5c-692b-4fe8-8689-432c6c432694
spec:
argoServer:
argoNamespace: openshift-gitops
cluster: local-cluster
placementRef:
apiVersion: cluster.open-cluster-management.io/v1beta1
kind: Placement
name: all-openshift-clusters
status:
lastUpdateTime: "2023-06-19T08:44:00Z"
message: Added managed clusters [sagrawal-nc1 sagrawal-nc2] to gitops namespace
openshift-gitops
phase: successful
kind: List
metadata:
resourceVersion: ""
$ oc get placement -n openshift-gitops -o yaml
apiVersion: v1
items:
- apiVersion: cluster.open-cluster-management.io/v1beta1
kind: Placement
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"cluster.open-cluster-management.io/v1beta1","kind":"Placement","metadata":{"annotations":{},"name":"all-openshift-clusters","namespace":"openshift-gitops"},"spec":{"predicates":[{"requiredClusterSelector":{"labelSelector":{"matchExpressions":[{"key":"vendor","operator":"In","values":["OpenShift"]}]}}}],"tolerations":[{"key":"cluster.open-cluster-management.io/unreachable","operator":"Exists"},{"key":"cluster.open-cluster-management.io/unavailable","operator":"Exists"}]}}
creationTimestamp: "2023-06-19T07:21:10Z"
generation: 1
name: all-openshift-clusters
namespace: openshift-gitops
resourceVersion: "3647442"
uid: b107abbb-f0c3-4d89-af1e-00a94c7982fe
spec:
predicates:
- requiredClusterSelector:
labelSelector:
matchExpressions:
- key: vendor
operator: In
values:
- OpenShift
tolerations:
- key: cluster.open-cluster-management.io/unreachable
operator: Exists
- key: cluster.open-cluster-management.io/unavailable
operator: Exists
status:
conditions:
- lastTransitionTime: "2023-06-19T07:21:10Z"
message: Placement configurations check pass
reason: Succeedconfigured
status: "False"
type: PlacementMisconfigured
- lastTransitionTime: "2023-06-19T07:21:10Z"
message: All cluster decisions scheduled
reason: AllDecisionsScheduled
status: "True"
type: PlacementSatisfied
numberOfSelectedClusters: 2
kind: List
metadata:
resourceVersion: ""
- is cloned by
-
-
- Closed
-
- links to
-
RHSA-2023:120161
Red Hat Advanced Cluster Management 2.8.2 bug fixes and container updates
