Machines stuck in “starting” state

[dangra]

Hello. This turned out to be a tricky bug for which @rian found the solution

Fixed: unreasonably slow resumes of suspended Machines

We fixed a bug that caused a small number of Fly Machines to take way too long to resume from the suspended state - sometimes over 30 seconds for tiny 256MB machines. If your machine was affected, resume times could get worse with each suspend/resume cycle until you rebooted. Machines need to be updated for the fix to take effect. If you don’t want to deploy, you can make an arbitrary metadata change with fly machine update <machine-id> --yes --metadata foo=bar to force an update. What was hap…