flyctl claims to deploy successfully then exits with an error

I’m deploying to fly from CircleCI, and most of my builds are failing even though flyctl’s output suggests that it’s succeeding:

v151 is being deployed
 1 desired, 1 placed, 0 healthy, 0 unhealthy
 1 desired, 1 placed, 0 healthy, 0 unhealthy [health checks: 1 total]
 1 desired, 1 placed, 0 healthy, 0 unhealthy [health checks: 1 total]
 1 desired, 1 placed, 0 healthy, 0 unhealthy [health checks: 1 total, 1 critical]
 1 desired, 1 placed, 0 healthy, 0 unhealthy [health checks: 1 total, 1 passing]
 1 desired, 1 placed, 1 healthy, 0 unhealthy [health checks: 1 total, 1 passing]
--> v151 deployed successfully

--> Troubleshooting guide at https://fly.io/docs/getting-started/troubleshooting/
Error abort

Exited with code exit status 1
CircleCI received exit code 1

v148 is being deployed
 1 desired, 1 placed, 0 healthy, 0 unhealthy [health checks: 1 total, 1 critical]
 1 desired, 1 placed, 0 healthy, 0 unhealthy [health checks: 1 total, 1 passing]
 1 desired, 1 placed, 1 healthy, 0 unhealthy [health checks: 1 total, 1 passing]
 1 desired, 1 placed, 1 healthy, 0 unhealthy [health checks: 1 total, 1 passing]
--> v148 deployed successfully

--> Troubleshooting guide at https://fly.io/docs/getting-started/troubleshooting/
Error abort

Exited with code exit status 1
CircleCI received exit code 1

Version: flyctl v0.0.296 linux/amd64 Commit: 25eb4c5 BuildDate: 2022-02-08T18:17:06Z

This sometimes happen when there are parallel deploys. You can sometimes see this by watching the version numbers in logs, if it goes from monitoring v150 to v151 the CLI thinks the deploy failed and it’s now monitoring a rollback.

If you run fly releases list you can see if they really succeeded or not.

Ah, gotcha. Thanks!

1 Like