Is this happening consistently? Are you on the latest flyctl version?
it would be nice to get back an exit code other than zero
i’ll see how easy it is to add that. hopefully others aren’t relying on the 0 we’re returning 
That was on v0.1.45 and I noticed it basically just today (happened maybe twice in a timespan of 15 minutes). One of the two machines did not start (stuck in created) and the deploy process timed out (region fra).
weird. your machine did start some milliseconds later. will see if i can figure out what went wrong there.
Just to let you know: Deploys are failing again because one machine does not reach “started” (e.g. 080eeeea64d318).
ok so machine 080eeeea64d318 was never started.
same with 2874445c029208. (i looked at the wrong machine_id earlier on)
i’m not sure what’s going on here. maybe increase your wait timeout a bit?
// wait for 5 minutes
fly deploy --wait-timeout 300
I’ll try that next.
Now I am actually not seeing any of the bluegreen outputs of preparing multiple machines, just this:
--> Pushing image done
image: registry.fly.io/...:deployment-01H4EP54BS9A65K7PH9S3FJ329
image size: 851 MB
Watch your app at https://fly.io/apps/.../monitoring
And there the process keeps waiting. SIGINT does not work either (process does not exit). This is on fly v0.1.47.
Update on my latest posts: I haven’t seen the erratic behavior since about a day. So 
I get a timeout waiting for my builder to start when I switch to bluegreen, and I don’t know why:
Using flyctl 0.1.56:
Waiting for 148ed677a47078 to have state: started
Error: release command failed - aborting deployment. error waiting for release_command machine 148ed677a47078 to start: timeout reached waiting for machine to started failed to wait for VM
Deploys are usually fine, this is a small cluster with no volumes attached – nothing special about it.
2 Likes
Destroying the builder also has no effect.
hey @shugel, at the moment, I don’t have any idea why your release commands are timing out. Bluegreen doesn’t affect release commands, you’re probably running into a different issue altogether.
This was important for our app’s migration, thank you!
1 Like
Just to cross reference this post What is happening with flyctl? - #16 by kwaw as some of us are having issues with the deployments randomly failing, and it may have something to do with bluegreen.