Unable to kill old VM instance after deploying a new version. I have ran ‘vm stop 3dd06b9c’ without any success. I think I need help from Fly directly to resolve the issue unless there is some other command to force kill this instance.
Hi @themaxsmith, thanks for reporting, you’re correct it was an internal platform issue.
One of our hosts in the sjc region triggered a bug in Nomad (our VM-orchestration service), which was preventing some instances (including yours) from getting updated correctly. We restarted the service on the affected host which unblocked the stuck instances. Sorry for the inconvenience!