-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.13
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
Proposed
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
newly imported managed cluster not updated to window.SERVER_FLAGS.clusters, the first managed cluster info can be successfully included in window.SERVER_FLAGS.clusters but following new managed clusters will not be included which causes newly imported clusters are not shown in 'All Clusters' dropdown
Version-Release number of selected component (if applicable):
4.13.0-0.nightly-2023-02-01-112003
How reproducible:
Always
Steps to Reproduce:
1. Enable multi-cluster feature gate
2. Import one managed clusters 'mng1-175232', wait for cluster is joined successfully, refresh console, check cm/managed-clusters, window.SERVER_FLAGS.clusters and window.SERVER_FLAGS.copiedCSVsDisabled
$ oc get managedclusters
NAME HUB ACCEPTED MANAGED CLUSTER URLS JOINED AVAILABLE AGE
local-cluster true https://api.yapei12374.qe.devcluster.openshift.com:6443 True True 74m
mng1-175232 true https://api.yapeimg1.qe.azure.devcluster.openshift.com:6443 True True 19m True 19m
$ oc get cm managed-clusters -n openshift-console -o yaml
apiVersion: v1
data:
managed-clusters.yaml: |
- name: mng1-175232
apiServer:
url: https://api.yapeimg1.qe.azure.devcluster.openshift.com:6443
caFile: /var/managed-cluster-api-server-certs/mng1-175232-managed-cluster-api-server-cert/ca-bundle.crt
oauth:
clientID: console-managed-cluster-oauth-client
clientSecret: 2X10Pzo9TUeWCky08I4F1rHNxst_aHehhyf4-TSFX70
caFile: /var/managed-cluster-oauth-server-certs/mng1-175232-managed-cluster-oauth-server-cert/ca-bundle.crt
copiedCSVsDisabled: false
$ > window.SERVER_FLAGS.copiedCSVsDisabled
< {local-cluster: false, mng1-175232: false}
$ > window.SERVER_FLAGS.clusters
< ["local-cluster", "mng1-175232"] (2)
3. Import one more managed cluster 'mng2-175234', wait for cluster is joined successfully, refresh console, check cm/managed-clusters, window.SERVER_FLAGS.clusters and window.SERVER_FLAGS.copiedCSVsDisabled
$ oc get managedclusters
NAME HUB ACCEPTED MANAGED CLUSTER URLS JOINED AVAILABLE AGE
local-cluster true https://api.yapei12374.qe.devcluster.openshift.com:6443 True True 81m
mng1-175232 true https://api.yapeimg1.qe.azure.devcluster.openshift.com:6443 True True 25m
mng2-175234 true https://api.yapeimg2.qe.gcp.devcluster.openshift.com:6443 True True 19m
$ oc get cm managed-clusters -n openshift-console -o yaml
apiVersion: v1
data:
managed-clusters.yaml: |
- name: mng1-175232
apiServer:
url: https://api.yapeimg1.qe.azure.devcluster.openshift.com:6443
caFile: /var/managed-cluster-api-server-certs/mng1-175232-managed-cluster-api-server-cert/ca-bundle.crt
oauth:
clientID: console-managed-cluster-oauth-client
clientSecret: 2X10Pzo9TUeWCky08I4F1rHNxst_aHehhyf4-TSFX70
caFile: /var/managed-cluster-oauth-server-certs/mng1-175232-managed-cluster-oauth-server-cert/ca-bundle.crt
copiedCSVsDisabled: false
- name: mng2-175234
apiServer:
url: https://api.yapeimg2.qe.gcp.devcluster.openshift.com:6443
caFile: /var/managed-cluster-api-server-certs/mng2-175234-managed-cluster-api-server-cert/ca-bundle.crt
oauth:
clientID: console-managed-cluster-oauth-client
clientSecret: 2X10Pzo9TUeWCky08I4F1rHNxst_aHehhyf4-TSFX70
caFile: /var/managed-cluster-oauth-server-certs/mng2-175234-managed-cluster-oauth-server-cert/ca-bundle.crt
copiedCSVsDisabled: false
kind: ConfigMap
$ > window.SERVER_FLAGS.copiedCSVsDisabled
< {local-cluster: false, mng1-175232: false}
$ > window.SERVER_FLAGS.clusters
< ["local-cluster", "mng1-175232"] (2)
Actual results:
From step3 result, we can see the newly imported managed cluster data is successfully written in cm/managed-clusters, and the cluster has been joined about 19minutes ago, however the newly added managed cluster still doesn't appear in 'All Clusters' dropdown, and window.SERVER_FLAGS.clusters values are not updated to include new managed clusters
Expected results:
managed clusters newly imported should be synced timely and shown up in 'All Clusters' dropdown
Additional info: