My deploys have stopped working

1

I’ve just noticed that my deploys from CI have stopped working. Appears to have been happening for a few days now. If I deploy from my machine it works fine. I don’t recall changing anything related to my deployment lately, so this is weird.

Here’s the logs from github actions:

deployment-01HQ7H6PAYA22ZDP72305SHPJ7: digest: sha256:30d268196d5ebf505abf1939c80e337b65122f490e18ee48cad652211afaded2 size: 2411
--> Pushing image done
image: registry.fly.io/ott-staging:deployment-01HQ7H6PAYA22ZDP72305SHPJ7
image size: 997 MB
Watch your deployment at https://fly.io/apps/ott-staging/monitoring
Running ott-staging release_command: yarn run db:migrate
> Created release_command machine d891112f466258
> Waiting for d891112f466258 to have state: started
> Machine d891112f466258 has state: started
> Waiting for d891112f466258 to have state: destroyed
> Machine d891112f466258 has state: destroyed
> Waiting for d891112f466258 to get exit event
✔ release_command d891112f466258 completed successfully
> Creating canary machine for group app
> Machine 287444ec627238 [app] was created
> Checking that 287444ec627238 [app] is up and running
> Waiting for 287444ec627238 [app] to have state: started
> Machine 287444ec627238 [app] has state: started
> Waiting for 287444ec627238 [app] to become healthy: 0/1
WARN failed to release lease for machine 287444ec627238: lease not found
✖ Failed to create canary machine: timeout reached waiting for health checks to pass for machine 287444ec627238: failed to get VM 287444ec627238: Get "https://api.machines.dev/v1/apps/ott-staging/machines/287444ec627238": net/http: request canceled
Checking DNS configuration for ott-staging.fly.dev
Error: timeout reached waiting for health checks to pass for machine 287444ec627238: failed to get VM 287444ec627238: Get "https://api.machines.dev/v1/apps/ott-staging/machines/287444ec627238": net/http: request canceled
Your machine never reached the state "%s".
You can try increasing the timeout with the --wait-timeout flag
Error: Process completed with exit code 1.

I’m using the canary deploy strategy. For fly people, the apps are ott-prod and ott-staging. Is anyone else experiencing this?

2

Hey @dyc3 ,

It seems the new deploy might be failing its heath checks. What do you see when you run fly logs for either of the apps?

3

Just tried a new deploy. Nothing’s wrong on Fly’s end, something changed with my builds that caused the build to go to a new directory.

1 Like
4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.