-
Bug
-
Resolution: Done
-
Critical
-
None
-
4.13
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
Proposed
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
When switching to one of the managed clusters, we see many Gateway Time-out errors, the managed cluster web console never gets loaded
Version-Release number of selected component (if applicable):
4.13.0-0.nightly-2023-01-08-161419
How reproducible:
very often
Steps to Reproduce:
1. Enable multi-cluster feature on 4.13 cluster(we need to enable feature-gate temporarily) 2. Import '170170' as managed cluster, wait for '170170' appear in the 'All Clusters' dropdown $ oc get managedcluster NAME HUB ACCEPTED MANAGED CLUSTER URLS JOINED AVAILABLE AGE 170170 true https://api.huliu-aws9c.qe.devcluster.openshift.com:6443 True True 6m28s local-cluster true https://api.yapei413bug.qe.devcluster.openshift.com:6443 True True 6h47m 3. Switch to '170170', type login username and password
Actual results:
3. We can see many '504 Gateway Time-out' errors and managed cluster web never gets loaded For example Error when reading infrastructure CR: a: Gateway Time-out https://console-openshift-console.apps.yapei413bug.qe.devcluster.openshift.com/api/kubernetes/apis/apiextensions.k8s.io/v1/customresourcedefinitions?limit=250&cluster=170170 [HTTP/1.1 504 Gateway Time-out 30317ms we can see errors in console pod I0110 08:30:45.571716 1 proxy.go:105] PROXY: `https://cluster-proxy-addon-user.multicluster-engine.svc:9092/170448/apis/apiextensions.k8s.io/v1/customresourcedefinitions` 2023/01/10 08:30:47 http: proxy error: context canceled 2023/01/10 08:30:57 http: proxy error: context canceled 2023/01/10 08:31:07 http: proxy error: context canceled 2023/01/10 08:31:15 http: proxy error: context canceled I0110 08:31:30.859035 1 proxy.go:105] PROXY: `https://cluster-proxy-addon-user.multicluster-engine.svc:9092/170448/apis/apiextensions.k8s.io/v1/customresourcedefinitions` 2023/01/10 08:32:00 http: proxy error: context canceled I0110 08:32:16.159344 1 proxy.go:105] PROXY: `https://cluster-proxy-addon-user.multicluster-engine.svc:9092/170448/apis/apiextensions.k8s.io/v1/customresourcedefinitions` 2023/01/10 08:32:46 http: proxy error: context canceled I0110 08:33:01.463513 1 proxy.go:105] PROXY: `https://cluster-proxy-addon-user.multicluster-engine.svc:9092/170448/apis/apiextensions.k8s.io/v1/customresourcedefinitions` 2023/01/10 08:33:31 http: proxy error: context canceled I0110 08:33:47.261121 1 proxy.go:105] PROXY: `https://cluster-proxy-addon-user.multicluster-engine.svc:9092/170448/apis/apiextensions.k8s.io/v1/customresourcedefinitions` 2023/01/10 08:34:17 http: proxy error: context canceled I0110 08:34:32.542371 1 proxy.go:105] PROXY: `https://cluster-proxy-addon-user.multicluster-engine.svc:9092/170448/apis/apiextensions.k8s.io/v1/customresourcedefinitions` I0110 08:34:58.015794 1 proxy.go:105] PROXY: `https://cluster-proxy-addon-user.multicluster-engine.svc:9092/170448/openapi/v2` 2023/01/10 08:35:02 http: proxy error: context canceled I0110 08:35:17.830057 1 proxy.go:105] PROXY: `https://cluster-proxy-addon-user.multicluster-engine.svc:9092/170448/apis/apiextensions.k8s.io/v1/customresourcedefinitions` 2023/01/10 08:35:28 http: proxy error: context canceled 2023/01/10 08:35:47 http: proxy error: context canceled I0110 08:36:03.127173 1 proxy.go:105] PROXY: `https://cluster-proxy-addon-user.multicluster-engine.svc:9092/170448/apis/apiextensions.k8s.io/v1/customresourcedefinitions` 2023/01/10 08:36:33 http: proxy error: context canceled
Expected results:
3. managed cluster web should be loaded successfully and user can switch between managed clusters correctly
Additional info:
