aws-amplify / aws-amplify/amplify-hosting

An error occurred during the push operation: Cannot iteratively rollback as the following step does not contain a previousMetaKey: {"status":"DEPLOYING"}

Open
#2,582 7 comments 2 reactions 0 assignees View on GitHub
Dominant language
Dockerfile
Stars
481
Forks
123
PR merge metrics
No merged PRs in 30d

Description

### Before opening, please confirm:

- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-console/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-console/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-console/blob/master/CONTRIBUTING.md).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

### App Id

d3oybpl8qpijc0 --envName stage

### Region

ap-norteast-1

### Amplify Console feature

_No response_

### Describe the bug

amplify push fails with error:
`
An error occurred during the push operation: Cannot iteratively rollback as the following step does not contain a previousMetaKey: {"status":"DEPLOYING"}`

(I had once this command results with unusual status like: deploying in the cloud... - instead of usual digest of app params)

### Expected behavior

{"status":"DEPLOYING"} must be temporary status ending up with some final status

### Reproduction steps

amplify push

(I had once this command results with unusual status like: deploying in the cloud... - instead of usual digest of app params)

### Build Settings

_No response_

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reviewing FAQ.md and CONTRIBUTING.md, then reproduce the failure with amplify push for app d3oybpl8qpijc0 in the stage environment and ap-norteast-1 region. Trace the deployment status handling around the reported rollback error; done means the push no longer fails on the temporary DEPLOYING status and reaches a final status.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.