deployments appear to be stuck

1

I’m seeing this error where deployments appear to be stuck. I already tried a number of things:

  • delete my app and recreate it
  • remove the release_command from the config file
  • change strategy to immediate

Nothing seems to help, the monitoring panel just shows Waiting for logs....

Is there an known issue? https://status.flyio.net/ shows all is ok

3 Likes
2

I’m having the same problem

3

Same here. Deployment (via GitHub actions) has been stuck for 20 minutes and counting.

image
image1542×596 46 KB

image
image760×400 40.6 KB

4

Same here got an alert for API not-responsive. Tried to redeploy and the instance is in limbo.

5

Same, though there seems to be some progress (Starting instance logs, but nothing more)

6

Same here. After a long period of “starting instance” I get “unhealthy allocations” error.

7

Same, stuck on "Running release task (pending)..."

8

Perhaps related, we also can not deploy:

image
image1380×374 36.3 KB

Automatically canceled after reaching our timeout (10 minutes)

App staxcloud-prod

9

Same, and the running app that I had was randomly killed (SIGINT - like reported in Virtual machine repeatedly shutting down App killed)

10

One VM is starting now: The only one that we have running in ams. The others that are running in fra aren’t starting yet.

That’s the same region that @alejrpo3234 mentioned in the post he just linked.

11

Seem to be working again. But deployments remain slow.

12

the fra regions seems to have issues. I can’t get a stable deploy to it

vscode ➜ /workspaces/sumiu (main ✗) $ fly regions list
Region Pool:
fra
gru
Backup Region:
vscode ➜ /workspaces/sumiu (main ✗) $ fly scale count 2 --max-per-region=1
Count changed to 2
vscode ➜ /workspaces/sumiu (main ✗) $

fly kept pushing a deployment to gru no matter what but now the command does nothing

edit: added a couple more of regions with fly regions add and they all got deployed perfectly except fra

13

Our fra region is experiencing high load resulting in slower deployments (sometimes 10-15 minutes or longer). The fly deploy command can timeout in those cases. When that happens the deployment will still happen, and once it does fly status will show the instances as running.

More info on our status page: Fly.io Status - Deployments may take 10-15min in fra region

1 Like