We have tried to run multiple releases in the last hour or so and they all stay stuck right at the beginning:
==> Creating release
--> release v576 created
--> You can detach the terminal anytime without stopping the deployment
==> Release command detected: /app/bin/homer eval Homer.Release.migrate
--> This release will not be available until the release command succeeds.
I don’t see any incident related to this issue on the status page. Could you help us out?
This is happening on two of our applications, bitter-wave-3155 and shy-wind-3844.
Not sure if it’s the same issue but I’ve got a release that seems to be stuck, too: Simplify how to find the next form step · PREreview/prereview.org@978184b · GitHub successfully deployed to the prereview app, but the new release for the prereview-sandbox app (v188) seems to be stuck. GitHub Actions isn’t showing me any output; the Fly.io dashboard is showing me the same as running flyctl status:
Deployment Status
ID = af5ce42a-f807-4003-c21d-9c021db6234c
Version = v188
Status = running
Description = Deployment is running
Instances = 1 desired, 0 placed, 0 healthy, 0 unhealthy
I can’t see a way to see the logs from the failing deployment (only the logs from the running v187 instance).
It’s been stuck for over an hour now. I’ve left the GitHub action running, but can probably safely cancel that. I assume that won’t cancel the release itself, though. I can’t see an option to do that, either.