sticky-summer-13450
12/04/2022, 12:56 PM$ kubectl logs deployment/rancher -n cattle-system --context=harvester --since=1m --follow
...
evicting pod longhorn-system/instance-manager-r-1503169c
evicting pod longhorn-system/instance-manager-e-029f5eba
error when evicting pods/"instance-manager-r-1503169c" -n "longhorn-system" (will retry after 5s): Cannot evict pod as it would violate the pod's disruption budget.
error when evicting pods/"instance-manager-e-029f5eba" -n "longhorn-system" (will retry after 5s): Cannot evict pod as it would violate the pod's disruption budget.
evicting pod longhorn-system/instance-manager-r-1503169c
evicting pod longhorn-system/instance-manager-e-029f5eba
error when evicting pods/"instance-manager-e-029f5eba" -n "longhorn-system" (will retry after 5s): Cannot evict pod as it would violate the pod's disruption budget.
error when evicting pods/"instance-manager-r-1503169c" -n "longhorn-system" (will retry after 5s): Cannot evict pod as it would violate the pod's disruption budget.
evicting pod longhorn-system/instance-manager-r-1503169c
evicting pod longhorn-system/instance-manager-e-029f5eba
FWIW I got bored after watching them for around 15 minutes and killed the pods myself:
$ kubectl delete pod instance-manager-r-1503169c -n "longhorn-system" --context=harvester; kubectl delete pod instance-manager-e-029f5eba -n "longhorn-system" --context=harvester
Which got the upgrade moving again.
This happened at the post-drained phase of the 2nd and 3rd nodes of a 3 node Harvester cluster.salmon-city-57654
12/04/2022, 5:13 PMsticky-summer-13450
12/04/2022, 5:14 PMsalmon-city-57654
12/05/2022, 4:27 PMsticky-summer-13450
12/05/2022, 5:18 PM