"Error lease not found" when doing "fly deploy"

[sasha]

I’ve seen Error lease not found a few times when doing fly deploy --remote-only
Everything builds fine, and works if I retry.
What could be going wrong?

...
deployment-1659486927: digest: sha256:054ca851a5d274d20b4c2469c3b630f9b489f2738d242b8227351ac6f346033c size: 2424
--> Pushing image done
image: registry.fly.io/s-machine:deployment-1659486927
image size: 2.3 GB
Deploying with rolling strategy
Taking lease out on VM 591857e0a79d83
Updating VM 591857e0a79d83
Waiting for update to finish on 591857e0a79d83
Error lease not found

[kurt]

This is just a bug in the deploy process for machine apps. The lease is timing out before we attempt to remove it. This’ll get fixed before we make machine apps the default.

[harsh-98]

getting this error still failed to release lease for machine 9080540c6ede58: lease not found.

[bryantbrock]

Just received this error when run in a Github Action, running the deploy locally didn’t show this error.

[mraaroncruz]

I’m getting this currently with a fly secrets set

[jpeckiii]

Is there any update on this? I’m also getting this on a deployment using the Remix Blues Stack.

[Uninen]

I also bumped into this using Github Actions. Would be nice to have at least a workaround as having flaky deployments sucks big time.

[hyerdev]

I’m getting the same error in github action: