sureshanaparti commented on PR #6522:
URL: https://github.com/apache/cloudstack/pull/6522#issuecomment-1180016887

   The test failure above is not related to the changes here, seems to be env 
issue (or can be some issue with kubernetes cluster upgrade)
   
   ```
   I0711 05:47:52.762412  4527 request.go:533] Waited for 185.482967ms due to 
client-side throttling, not priority and fairness, request: 
PUT:https://10.0.58.203:6443/apis/rbac.authorization.k8s.io/v1/namespaces/kube-system/rolebindings/kube-proxy?timeout=10s
   Warning: resource secrets/kubernetes-dashboard-key-holder is missing the 
kubectl.kubernetes.io/last-applied-configuration annotation which is required 
by kubectl apply. kubectl apply should only be used on resources created 
declaratively by either kubectl create --save-config or kubectl apply. The 
missing annotation will be patched automatically.
   Error from server (Timeout): error when retrieving current configuration of:
   Resource: "/v1, Resource=namespaces", GroupVersionKind: "/v1, Kind=Namespace"
   Name: "kubernetes-dashboard", Namespace: ""
   from server for: "/mnt/k8sdisk//dashboard.yaml": the server was unable to 
return a response in the time allotted, but may still be processing the request 
(get namespaces kubernetes-dashboard)
   
   2022-07-11 05:49:12,672 ERROR [c.c.k.c.a.KubernetesClusterActionWorker] 
(API-Job-Executor-16:ctx-93039a46 job-4074 ctx-506a9493) (logid:7f11d73f) 
Failed to upgrade Kubernetes cluster : testcluster-DQ9GSE, unable to upgrade 
Kubernetes node on VM : testcluster-DQ9GSE-control-181ebc5f82c
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to