I upgraded my Rancher installation (standalone docker container) and there are two messages in the Rancher log popping up every second:
time="2020-10-09T18:00:31.837530296Z" level=info msg="Waiting for containerd startup: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService" time="2020-10-09T18:00:32.063809685Z" level=info msg="Waiting for master node local-node startup: nodes \"local-node\" not found"
Clicking on ‘local’ cluster opens page with ‘Graph information from Cluster currently not available’ and it has 0 nodes.
Other cluster (the one that was managed by Rancher before) seems to be OK and functional.
UPDATE: after VM restart I’m not seeing these 2 log messages, but there are these logs now:
[storage/driver] 2020/10/09 18:36:04 query: failed to query with labels: the server could not find the requested resource (get configmaps) UPGRADE FAILED Error: the server could not find the requested resource (get configmaps) 2020/10/09 18:36:04 [ERROR] AppController p-m9qr2/rancher-k3s-upgrader [helm-controller] failed with : failed to install app rancher-k3s-upgrader. Error: UPGRADE FAILED: the server could not find the requested resource (get configmaps) E1009 18:36:20.846641 25 scheduler.go:638] error selecting node for pod: no nodes available to schedule pods
Local cluster state seems to be stuck in ‘Upgrading’.
Is there any way to bring it back to normal or is it normal?