I tried to kill the vm but nothing happens.
Edit: v81 disappeared and v85 status changed to running. But v79 is still running.
Sorry I thought the issue got resolved on its own but when I tried to deploy a new version it got stuck on release message. I tried to do something but I am back to where I was. Here are the new instances
Hi @namus, thanks for reporting this.
It looks like a server in the maa region got disconnected from our global VM scheduler (nomad), causing your VMs to get stuck in that pending state, I’ve restarted the service and confirmed they are no longer pending. Sorry for the inconvenience, this issue is very much on our radar and we’re looking into improvements to make this more reliable.
1 Like