Hi,
I am trying to deploy changes in LAX region. Deployment is stuck in created state, it is not launching new machines.
Your post is rather brief, and there may not be enough information to help you. Consider adding more information; read this opinion post for suggestions.
I have my backend application deployed in LAX region, it was up and running. When I tried to push my changes and deploy, it got stuck in launch status.
Tried to delete the existing machine and lauch new machine with latest changes, still no luck.
Deployment is started, machine is created and pending in launch.
Not sure any issue in LAX region. However, wnated to get input on the same.
I am executing below command to deploy my latest changes to fly.io app running in LAX region.
flyctl deploy --remote-only --ha=false --wait-timeout 300
After docker build, it is creating the container, but not starting. Below is log.
Logs:
Process groups have changed. This will:
- create 1 “app” machine
No machines in group app, launching a new machine
WARN failed to release lease for machine 87149eb6339508 [app]: lease not found
Failed: timeout reached waiting for machine’s state to change
Error: timeout reached waiting for machine’s state to change
Your machine was created, but never started or exited immediately. This could mean that your app is taking a long time to start,
but it could be indicative of a region issue.
Thanks for the additional details… Try running fly logs in a separate terminal window (and leaving it running there) and then do a fly deploy again. This will give you the logs from within the Machine itself (and the associated infrastructure), which are different from what you posted above. Look in particular for messages about insufficient capacity.
I just tried creating a Machine in LAX and didn’t see any problems, so I don’t think it’s a region-wide glitch.
It would also help if you could post the output of fly m list and your full fly.toml. You can use the </> button in the toolbar to get an area suitable for pasting code, output, etc.