I'm still having trouble with a 1.4.3-1.5.1 upgrade> everything I've read now points to reaching out to support - essentially the upgrade is stat waiting for a volume that is deleting to come online and has been this way for nearly 2 months...

++ kubectl get <http://volumes.longhorn.io/pvc-2d047b5c-cc51-4775-8a22-0eadc9d9656f|volumes.longhorn.io/pvc-2d047b5c-cc51-4775-8a22-0eadc9d9656f> -n longhorn-system -o 'jsonpath={.status.robustness}'
+ robustness=degraded
+ '[' degraded = healthy ']'
+ '[' -f /tmp/skip-pvc-2d047b5c-cc51-4775-8a22-0eadc9d9656f ']'
+ echo 'Waiting for volume pvc-2d047b5c-cc51-4775-8a22-0eadc9d9656f to be healthy...'
+ sleep 10
Waiting for volume pvc-2d047b5c-cc51-4775-8a22-0eadc9d9656f to be healthy...

I would restart the process but the guides say not to unless advised. I'm also now considering scaling this cluster down and building a latest version cluster and migrating the resources across manually - since this is used mainly for development and there is plenty of capacity. Any pointers greatly appreciated!

If you look at the loop's logic, it just wants that volume to be healthy, so you could start a bogus deployment that mounts that PVC, let Longhorn rebuild it and then afterwards delete all of it.

Thanks - may well give that a try - wont be until mid-week now...