shwstppr commented on pull request #4411:
URL: https://github.com/apache/cloudstack/pull/4411#issuecomment-713425194
@DaanHoogland seems like some network issue in env during cluster upgrade.
Failed from kubeadm itself. Doesn't seem related to PR changes,
```
121340 2020-10-20 16:37:14,144 ERROR [c.c.u.s.SshHelper]
(API-Job-Executor-5:ctx-928e799d job-779 ctx-7bc68c76) (logid:a1a0ffa1) SSH
execution of command sudo ./upgrade-kuberntes13470214930726030527.sh 1
.16.0 false false false has an error status code in return. Result output:
Installing binaries from /mnt/k8sdisk/
121341 Loaded image: k8s.gcr.io/coredns:1.6.2
121342 Loaded image: k8s.gcr.io/etcd:3.3.15-0
121343 Loaded image: k8s.gcr.io/kube-apiserver:v1.16.0
121344 Loaded image: k8s.gcr.io/kube-controller-manager:v1.16.0
121345 Loaded image: k8s.gcr.io/kube-proxy:v1.16.0
121346 Loaded image: k8s.gcr.io/kube-scheduler:v1.16.0
121347 Loaded image: k8s.gcr.io/pause:3.1
121348 [upgrade] Reading configuration from the cluster...
121349 [upgrade] FYI: You can look at this config file with 'kubectl -n
kube-system get cm kubeadm-config -oyaml'
121350 unable to fetch the kubeadm-config ConfigMap: failed to get config
map: Get
https://10.1.1.234:6443/api/v1/namespaces/kube-system/configmaps/kubeadm-config:
dial tcp 10.1.1.234:6443: connect: conn ection refused
121351 To see the stack trace of this error execute with --v=5 or higher
121352
121353 2020-10-20 16:37:14,145 ERROR
[c.c.k.c.a.KubernetesClusterActionWorker] (API-Job-Executor-5:ctx-928e799d
job-779 ctx-7bc68c76) (logid:a1a0ffa1) Failed to upgrade Kubernetes cluster ID:
1c501beb-10 2e-49e2-8cb6-16b6056b1f96, unable to upgrade Kubernetes node
on VM ID: e911af24-3b44-40a0-918e-ac5c5abd31b4
```
If needed we can have another test run or test upgrade manually.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
