This message was deleted.

It might just be easier to delete the VM and re-create it. Cattle not pets...

No real advise, I'm just curious: Did you run the update while the VM was running? I'd also suggest checking Longhorn... it's only cattle when it's a Kubernetes node, otherwise it's a pet and you need to be able to fix it.

I didn't know how to check longhorn so I decided to cut my losses and rebuild. It was a kubernetes agent node, so I wasn't personally attached to it.