aws-amplify / aws-amplify/amplify-hosting

Backend Deployments Fail When Run at the Same Time

Open
#2,416 5 comments 0 reactions 1 assignee Assigned to @chrisbonifacio View on GitHub
bug transferred
Dominant language
Dockerfile
Stars
481
Forks
123
PR merge metrics
No merged PRs in 30d

Description

### Before opening, please confirm:

- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-js/issues?q=is%3Aissue+) and [discussions](https://github.com/aws-amplify/amplify-js/discussions).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-js/blob/main/CONTRIBUTING.md#bug-reports).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

### JavaScript Framework

Vue

### Amplify APIs

Not applicable

### Amplify Categories

_No response_

### Environment information

```
# Put output below this line
System:
OS: macOS 12.0.1
CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz
Memory: 42.09 MB / 8.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.6.1 - /usr/local/bin/node
Yarn: 3.1.0 - /usr/local/bin/yarn
npm: 7.23.0 - /usr/local/bin/npm
Browsers:
Chrome: 96.0.4664.55
Firefox: 93.0
Safari: 15.1
npmGlobalPackages:
@aws-amplify/cli: 7.5.2
aws-sdk: 2.983.0
minimist: 1.2.5
node-mailjet: 3.3.4
npm: 7.23.0
spaceship-prompt: 3.14.0
yarn: 1.22.11
```

### Describe the bug

```txt
2021-11-26T16:42:53.182Z [INFO]: Following resources failed
2021-11-26T16:42:53.184Z [WARNING]: ✖ An error occurred when pushing the resources to the cloud
2021-11-26T16:42:53.225Z [INFO]: 🛑 An error occurred during the push operation: Resource is not in the state stackUpdateComplete
2021-11-26T16:42:53.303Z [ERROR]: !!! Build failed
2021-11-26T16:42:53.304Z [ERROR]: !!! Non-Zero Exit Code detected
2021-11-26T16:42:53.304Z [INFO]: # Starting environment caching...
2021-11-26T16:42:53.304Z [INFO]: # Uploading environment cache artifact...
2021-11-26T16:42:53.369Z [INFO]: # Environment caching completed
```

It appears that the build disconnects from the CloudFormation stack update operation. The CLI build fails with only this information at various points during the build, and the CloudFormation build continues as normal.

### Expected behavior

The build should continue as normal without any stack update complete errors from appearing in the build console.

### Reproduction steps

It can be difficult to re-produce as it is extremely unclear what is causing it. It happens sporadically and usually occurs a lot when multiple developers are updating various stacks at the same time.

### Code Snippet

2021-11-26T16:42:53.182Z [INFO]: Following resources failed
2021-11-26T16:42:53.184Z [WARNING]: ✖ An error occurred when pushing the resources to the cloud
2021-11-26T16:42:53.225Z [INFO]: 🛑 An error occurred during the push operation: Resource is not in the state stackUpdateComplete
2021-11-26T16:42:53.303Z [ERROR]: !!! Build failed
2021-11-26T16:42:53.304Z [ERROR]: !!! Non-Zero Exit Code detected
2021-11-26T16:42:53.304Z [INFO]: # Starting environment caching...
2021-11-26T16:42:53.304Z [INFO]: # Uploading environment cache artifact...
2021-11-26T16:42:53.369Z [INFO]: # Environment caching completed

### Log output

_No response_

### aws-exports.js

_No response_

### Manual configuration

_No response_

### Additional configuration

_No response_

### Mobile Device

_No response_

### Mobile Operating System

_No response_

### Mobile Browser

_No response_

### Mobile Browser Version

_No response_

### Additional information and screenshots

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.