-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deployment fails for one environment #1046
Comments
Any tips to get it working again? Is the only option to remove the environment and set it up again? |
Hi @espenbye apologies for the delay. We are investigating this to find another potential workaround to get your environment out of this state and will update shortly. |
Is there any additional logging before or after the |
No worries. Since we was not able to get it up and working again, we just created a new environment- so it's no longer an issue for us. But let me know if you still need any logs |
For anyone else that ends up with a stuck deployment like this, one option is to go to the appropriate |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Before opening, please confirm:
App Id
d3pgmzdoktuvon
AWS Region
eu-north-1
Amplify Hosting feature
Backend builds
Describe the bug
We are unable to deploy to our development environment in Amplify. One of our deployments failed, and after that, we haven't been able to redeploy - the same code is running in other environments.
After running
amplify push
(either locally or via a build), we get the following error:Cannot iteratively rollback as the following step does not contain a previousMetaKey: {"status":"DEPLOYING"}
After searching for previous issues, some suggested deleting the
deployment-state.json
file from S3 and redeploying it. But unfortunately, that does not work either. After doing that, we receive the following error:🛑 ["Index: 0 State: {\"deploy\":\"waitingForDeployment\"} Message: Resource is not in the state stackUpdateComplete"]
Expected behavior
It should build and deploy.
Reproduction steps
Build Settings
No response
Log output
Additional information
No response
The text was updated successfully, but these errors were encountered: