When upgrading a Harvester cluster from v1.1.0 to v1.1.1, how long should I wait watching logs like this:

$ 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.

Hi @sticky-summer-13450, That looks like stuck on draining. Please show the related volume status. You could check the `instance-manager-r-1503169c`/`instance-manager-e-029f5eba` log to get more information. Thanks!

Sorry - as I said above, after watching them for around 15 minutes I got bored and killed the pods myself

OK, I miss this message. So after you killed those pods, the upgrade is continued and finally complete?

yes