Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Backend deployment issue #13562

Closed
2 tasks done
xanderbilla opened this issue Jan 29, 2024 · 3 comments
Closed
2 tasks done

Backend deployment issue #13562

xanderbilla opened this issue Jan 29, 2024 · 3 comments
Labels
pending-response Issue is pending response from the issue author pending-triage Issue is pending triage platform-push Issues related to `amplify push`

Comments

@xanderbilla
Copy link

How did you install the Amplify CLI?

npm

If applicable, what version of Node.js are you using?

v20.11.0

Amplify CLI Version

v12.10.1

What operating system are you using?

Windows

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

I don't think so

Describe the bug

I created react application using amplify as backend and added DynamoDB as my No sql database and s3 storage, but at the time of deployment the cloud formation failed, it never happened before.

Expected behavior

It should not happen.

Reproduction steps

  1. Added auth, DynamoDB, s3, API
  2. Edited the source file
  3. Uploaded to github
  4. Connected the branch and the deployment started

Project Identifier

No response

Log output

# Put your logs below this line
2024-01-28T22:12:18.977Z [INFO]: # Cloning repository: [email protected]:xanderbilla/Food-App.git
2024-01-28T22:12:21.417Z [INFO]: 
2024-01-28T22:12:21.418Z [INFO]: Cloning into 'Food-App'...
2024-01-28T22:12:21.418Z [INFO]: # Checking for Git submodules at: /codebuild/output/src908853964/src/Food-App/.gitmodules
2024-01-28T22:12:21.428Z [INFO]: # Retrieving environment cache...
2024-01-28T22:12:21.464Z [WARNING]: ! Unable to write cache: {"code":"ERR_BAD_REQUEST","message":"Request failed with status code 404"})}
2024-01-28T22:12:21.465Z [INFO]: ---- Setting Up SSM Secrets ----
2024-01-28T22:12:21.465Z [INFO]: SSM params {"Path":"/amplify/d36ge5vozfft98/dev/","WithDecryption":true}
2024-01-28T22:12:38.472Z [INFO]: # Patching NPM package '@aws-amplify/cli' from 10.5.2 to 12.10.1...
2024-01-28T22:12:56.650Z [INFO]: # Done patching NPM package '@aws-amplify/cli' to version 12.10.1
2024-01-28T22:12:56.740Z [INFO]: # Retrieving cache...
2024-01-28T22:12:56.785Z [INFO]: # Retrieved cache
2024-01-28T22:13:01.155Z [INFO]: ## Starting Backend Build
                                 # Starting phase: build
2024-01-28T22:13:03.409Z [INFO]: �[0mAmplify AppID found: d36ge5vozfft98. Amplify App name is: FoodApp�[0m
2024-01-28T22:13:03.449Z [INFO]: �[0mBackend environment dev found in Amplify Console app: FoodApp�[0m
2024-01-28T22:13:04.537Z [WARNING]: - Fetching updates to backend environment: dev from the cloud.
2024-01-28T22:13:05.131Z [WARNING]: - Building resource api/foodAppAPI
2024-01-28T22:13:05.173Z [WARNING]: - Building resource auth/foodappf1fa695a
2024-01-28T22:13:05.233Z [WARNING]: - Building resource storage/foodAppOrdersDB
2024-01-28T22:13:05.244Z [WARNING]: - Building resource storage/foodAppProdDB
2024-01-28T22:13:05.258Z [WARNING]: - Building resource storage/foodAppStorage
2024-01-28T22:13:05.292Z [WARNING]: ✔ Successfully pulled backend environment dev from the cloud.
2024-01-28T22:13:05.528Z [INFO]: ✅
2024-01-28T22:13:08.042Z [INFO]: �[33mNote: It is recommended to run this command from the root of your app directory�[39m
2024-01-28T22:13:09.034Z [WARNING]: - Initializing your environment: dev
2024-01-28T22:13:09.631Z [WARNING]: - Building resource api/foodAppAPI
2024-01-28T22:13:09.673Z [WARNING]: - Building resource auth/foodappf1fa695a
2024-01-28T22:13:09.729Z [WARNING]: - Building resource storage/foodAppOrdersDB
2024-01-28T22:13:09.741Z [WARNING]: - Building resource storage/foodAppProdDB
2024-01-28T22:13:09.751Z [WARNING]: - Building resource storage/foodAppStorage
2024-01-28T22:13:09.763Z [WARNING]: ✔ Initialized provider successfully.
2024-01-28T22:13:10.910Z [INFO]: �[0mNo AppSync API configured. Please add an API�[0m
2024-01-28T22:13:16.106Z [WARNING]: - Uploading files.
2024-01-28T22:13:20.561Z [WARNING]: - Uploading files.
2024-01-28T22:13:24.861Z [WARNING]: - Uploading files.
2024-01-28T22:13:29.172Z [WARNING]: - Uploading files.
2024-01-28T22:13:29.571Z [WARNING]: - Building resource api/foodAppAPI
2024-01-28T22:13:29.601Z [WARNING]: - Building resource auth/foodappf1fa695a
2024-01-28T22:13:29.650Z [WARNING]: - Building resource storage/foodAppOrdersDB
2024-01-28T22:13:29.667Z [WARNING]: - Building resource storage/foodAppProdDB
2024-01-28T22:13:29.673Z [WARNING]: - Building resource storage/foodAppStorage
2024-01-28T22:13:36.189Z [INFO]: 
2024-01-28T22:13:36.194Z [INFO]: UPDATE_IN_PROGRESS amplify-foodapp-dev-12950 AWS::CloudFormation::Stack Sun Jan 28 2024 22:13:31 GMT+0000 (Coordinated Universal Time) User Initiated
                                 UPDATE_IN_PROGRESS storagefoodAppOrdersDB    AWS::CloudFormation::Stack Sun Jan 28 2024 22:13:34 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS storagefoodAppStorage     AWS::CloudFormation::Stack Sun Jan 28 2024 22:13:34 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS storagefoodAppProdDB      AWS::CloudFormation::Stack Sun Jan 28 2024 22:13:34 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_FAILED      storagefoodAppStorage     AWS::CloudFormation::Stack Sun Jan 28 2024 22:13:35 GMT+0000 (Coordinated Universal Time) Parameters: [bucketName, unauthRoleName, unauthPolicyName, authRoleName, authPolicyName] must have values
                                 UPDATE_COMPLETE    storagefoodAppOrdersDB    AWS::CloudFormation::Stack Sun Jan 28 2024 22:13:36 GMT+0000 (Coordinated Universal Time)
2024-01-28T22:13:41.197Z [INFO]: 
2024-01-28T22:13:41.203Z [INFO]: UPDATE_FAILED               storagefoodAppProdDB      AWS::CloudFormation::Stack Sun Jan 28 2024 22:13:36 GMT+0000 (Coordinated Universal Time) Resource update cancelled
                                 UPDATE_ROLLBACK_IN_PROGRESS amplify-foodapp-dev-12950 AWS::CloudFormation::Stack Sun Jan 28 2024 22:13:37 GMT+0000 (Coordinated Universal Time) The following resource(s) failed to update: [storagefoodAppStorage, storagefoodAppProdDB].
2024-01-28T22:13:51.183Z [INFO]: 
2024-01-28T22:13:51.190Z [INFO]: UPDATE_COMPLETE                              storagefoodAppStorage     AWS::CloudFormation::Stack Sun Jan 28 2024 22:13:41 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS                           storagefoodAppOrdersDB    AWS::CloudFormation::Stack Sun Jan 28 2024 22:13:41 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE                              storagefoodAppProdDB      AWS::CloudFormation::Stack Sun Jan 28 2024 22:13:41 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE                              storagefoodAppOrdersDB    AWS::CloudFormation::Stack Sun Jan 28 2024 22:13:42 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS amplify-foodapp-dev-12950 AWS::CloudFormation::Stack Sun Jan 28 2024 22:13:43 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE                              storagefoodAppProdDB      AWS::CloudFormation::Stack Sun Jan 28 2024 22:13:44 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE                              storagefoodAppOrdersDB    AWS::CloudFormation::Stack Sun Jan 28 2024 22:13:44 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE                              storagefoodAppStorage     AWS::CloudFormation::Stack Sun Jan 28 2024 22:13:44 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_ROLLBACK_COMPLETE                     amplify-foodapp-dev-12950 AWS::CloudFormation::Stack Sun Jan 28 2024 22:13:44 GMT+0000 (Coordinated Universal Time)
2024-01-28T22:14:01.210Z [INFO]: �[K
2024-01-28T22:14:01.216Z [INFO]: 
2024-01-28T22:14:06.215Z [INFO]: 🛑 The following resources failed to deploy:
2024-01-28T22:14:06.221Z [INFO]: Resource Name: storagefoodAppStorage (AWS::CloudFormation::Stack)
                                 Event Type: update
                                 Reason: Parameters: [bucketName, unauthRoleName, unauthPolicyName, authRoleName, authPolicyName] must have values
                                 URL: https://console.aws.amazon.com/cloudformation/home?region=ap-south-1#/stacks/arn%3Aaws%3Acloudformation%3Aap-south-1%3A929910138721%3Astack%2Famplify-foodapp-dev-12950%2Fccc5e2b0-be17-11ee-aa33-022f42fafce5/events
                                 🛑 Resource is not in the state stackUpdateComplete
                                 Name: storagefoodAppStorage (AWS::CloudFormation::Stack), Event Type: update, Reason: Parameters: [bucketName, unauthRoleName, unauthPolicyName, authRoleName, authPolicyName] must have values, IsCustomResource: false
                                 Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
2024-01-28T22:14:06.221Z [WARNING]: ✖ There was an error initializing your environment.
2024-01-28T22:14:06.259Z [INFO]: 
2024-01-28T22:14:06.259Z [INFO]: Session Identifier: 0c8d1781-5246-428f-9643-717001164670
2024-01-28T22:14:06.261Z [WARNING]: - Creating Zip
2024-01-28T22:14:06.368Z [INFO]: ✅ Report saved: /tmp/FoodApp/report-1706480046272.zip
2024-01-28T22:14:06.368Z [WARNING]: - Sending zip
2024-01-28T22:14:08.455Z [WARNING]: ✔ Done
2024-01-28T22:14:08.456Z [INFO]: Project Identifier: dffcd85081d28c9763108fc3968b767a
2024-01-28T22:14:08.477Z [ERROR]: !!! Build failed
2024-01-28T22:14:08.477Z [ERROR]: !!! Non-Zero Exit Code detected
2024-01-28T22:14:08.477Z [INFO]: # Starting environment caching...
2024-01-28T22:14:08.478Z [INFO]: # Environment caching completed
Terminating logging...

Additional information

No response

Before submitting, please confirm:

  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.
@xanderbilla xanderbilla added the pending-triage Issue is pending triage label Jan 29, 2024
@ykethan
Copy link
Member

ykethan commented Jan 29, 2024

Hey @xanderbilla, thank you for reaching out. By any chance was the folder name of the project or the location changed locally? similar issue: #12315
Does amplify push locally throw the same error message?

@ykethan ykethan added pending-response Issue is pending response from the issue author platform-push Issues related to `amplify push` labels Jan 29, 2024
@ykethan
Copy link
Member

ykethan commented Feb 16, 2024

Closing due to inactivity @xanderbilla, do reach out to us if you are still experiencing this issue.

@ykethan ykethan closed this as not planned Won't fix, can't repro, duplicate, stale Feb 16, 2024
@github-actions GitHub Actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
pending-response Issue is pending response from the issue author pending-triage Issue is pending triage platform-push Issues related to `amplify push`
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@xanderbilla @ykethan