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.

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

amplify status failure during during aws serverless web app workshop #13336

Closed
2 tasks done
jeremymtx opened this issue Oct 16, 2023 · 5 comments
Closed
2 tasks done

amplify status failure during during aws serverless web app workshop #13336

jeremymtx opened this issue Oct 16, 2023 · 5 comments
Labels
pending-triage Issue is pending triage platform Issues tied to the general CLI platform

Comments

@jeremymtx
Copy link

How did you install the Amplify CLI?

npm install -g @aws-amplify/cli

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

18.8.1

Amplify CLI Version

12.7.0

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 made some GraphQL permissions changes to the small web app that I'm following along with in a AWS workshop (doing it independently). The changes were for using Amazon Cognito User Pool. After the changes were made, then ran the following:

amplify push --y (which ran successfully)
amplify status (which gives me an unknown error and creating a report)

Describe the bug

PS C:\Users\aghor\OneDrive\Documents\programming\aws\workshops\serverlessWebApp\jpm-event-planner> amplify status
🛑 UNKNOWN: unknown error, readlink 'C:\Users\aghor\OneDrive\Documents\programming\aws\workshops\serverlessWebApp\jpm-event-planner\amplify#current-cloud-backend\auth\userPoolGroups\user-pool-group-precedence.json'

Resolution: Please report this issue at https://github.com/aws-amplify/amplify-cli/issues and include the project identifier from: 'amplify diagnose --send-report'
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

Session Identifier: f08246ab-df3f-4f7a-9218-738996e60cfc

✅ Report saved: C:\Users\aghor\AppData\Local\Temp\jpmeventplanner\report-1697480942037.zip

Expected behavior

Rather than myeventplanner in the names, it would have been jpmeventplanner

expected_amplify_status_output

Reproduction steps

Ran through the steps at this AWS workshop page:

[https://catalog.us-east-1.prod.workshops.aws/workshops/1665a9b6-958b-4b70-ba52-14127b8fa99f/en-US/lab-2/step-3]

Project Identifier

05455eaefff208336a799d7ad1749802

Log output

# Put your logs below this line
2023-10-16T16:49:37.274Z|info : amplify-provider-awscloudformation.aws-s3.uploadFile.s3.putObject([{"Body":{"fd":null,"path":"C:\\Users\\aghor\\OneDrive\\Documents\\programming\\aws\\workshops\\serverlessWebApp\\jpm-event-planner\\amplify\\backend\\api\\jpmeventplanner\\schema.graphql","flags":"r","mode":438,"end":null,"bytesRead":0,"_readableState":{"objectMode":false,"highWaterMark":65536,"buffer":{"head":null,"tail":null,"length":0},"length":0,"pipes":[],"flowing":null,"ended":false,"endEmitted":false,"reading":false,"constructed":false,"sync":true,"needReadable":false,"emittedReadable":false,"readableListening":false,"resumeScheduled":false,"errorEmitted":false,"emitClose":true,"autoDestroy":true,"destroyed":false,"errored":null,"closed":false,"closeEmitted":false,"defaultEncoding":"utf8","awaitDrainWriters":null,"multiAwaitDrain":false,"readingMore":false,"dataEmitted":false,"decoder":null,"encoding":null},"_events":{},"_eventsCount":1},"Key":"[***]els/[***]lanner/[***]raphql","Bucket":"[***]ify-[***]lanner-[***]ev-[***]847-[***]ment"}])
2023-10-16T16:49:37.276Z|info : amplify-provider-awscloudformation.aws-s3.uploadFile.s3.putObject([{"Body":{"fd":null,"path":"C:\\Users\\aghor\\OneDrive\\Documents\\programming\\aws\\workshops\\serverlessWebApp\\jpm-event-planner\\amplify-codegen-temp\\models\\schema.js","flags":"r","mode":438,"end":null,"bytesRead":0,"_readableState":{"objectMode":false,"highWaterMark":65536,"buffer":{"head":null,"tail":null,"length":0},"length":0,"pipes":[],"flowing":null,"ended":false,"endEmitted":false,"reading":false,"constructed":false,"sync":true,"needReadable":false,"emittedReadable":false,"readableListening":false,"resumeScheduled":false,"errorEmitted":false,"emitClose":true,"autoDestroy":true,"destroyed":false,"errored":null,"closed":false,"closeEmitted":false,"defaultEncoding":"utf8","awaitDrainWriters":null,"multiAwaitDrain":false,"readingMore":false,"dataEmitted":false,"decoder":null,"encoding":null},"_events":{},"_eventsCount":1},"Key":"[***]els/[***]lanner/[***]a.js","Bucket":"[***]ify-[***]lanner-[***]ev-[***]847-[***]ment"}])
2023-10-16T16:49:37.278Z|info : amplify-provider-awscloudformation.aws-s3.uploadFile.s3.putObject([{"Body":{"fd":null,"path":"C:\\Users\\aghor\\OneDrive\\Documents\\programming\\aws\\workshops\\serverlessWebApp\\jpm-event-planner\\amplify-codegen-temp\\model-introspection.json","flags":"r","mode":438,"end":null,"bytesRead":0,"_readableState":{"objectMode":false,"highWaterMark":65536,"buffer":{"head":null,"tail":null,"length":0},"length":0,"pipes":[],"flowing":null,"ended":false,"endEmitted":false,"reading":false,"constructed":false,"sync":true,"needReadable":false,"emittedReadable":false,"readableListening":false,"resumeScheduled":false,"errorEmitted":false,"emitClose":true,"autoDestroy":true,"destroyed":false,"errored":null,"closed":false,"closeEmitted":false,"defaultEncoding":"utf8","awaitDrainWriters":null,"multiAwaitDrain":false,"readingMore":false,"dataEmitted":false,"decoder":null,"encoding":null},"_events":{},"_eventsCount":1},"Key":"[***]els/[***]lanner/[***]ction.json","Bucket":"[***]ify-[***]lanner-[***]ev-[***]847-[***]ment"}])
2023-10-16T18:28:31.342Z|info : amplify status core  {"yes":false}
2023-10-16T18:28:31.382Z|info : @aws-amplify/amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-10-16T18:28:39.553Z|error : UNKNOWN: unknown error, readlink 'C:\Users\aghor\OneDrive\Documents\programming\aws\workshops\serverlessWebApp\jpm-event-planner\amplify\#current-cloud-backend\auth\userPoolGroups\user-pool-group-precedence.json'
UnknownNodeJSFault: UNKNOWN: unknown error, readlink 'C:\Users\aghor\OneDrive\Documents\programming\aws\workshops\serverlessWebApp\jpm-event-planner\amplify\#current-cloud-backend\auth\userPoolGroups\user-pool-group-precedence.json'
2023-10-16T18:29:01.168Z|info : amplify status core  {"yes":false}
2023-10-16T18:29:01.207Z|info : @aws-amplify/amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-10-16T18:29:03.745Z|error : UNKNOWN: unknown error, readlink 'C:\Users\aghor\OneDrive\Documents\programming\aws\workshops\serverlessWebApp\jpm-event-planner\amplify\#current-cloud-backend\auth\userPoolGroups\user-pool-group-precedence.json'
UnknownNodeJSFault: UNKNOWN: unknown error, readlink 'C:\Users\aghor\OneDrive\Documents\programming\aws\workshops\serverlessWebApp\jpm-event-planner\amplify\#current-cloud-backend\auth\userPoolGroups\user-pool-group-precedence.json'
2023-10-16T18:37:51.734Z|info : amplify version core  
2023-10-16T18:42:40.555Z|info : amplify diagnose core  {"send-report":true,"yes":false}
2023-10-16T18:42:40.596Z|info : @aws-amplify/amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}

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.
@jeremymtx jeremymtx added the pending-triage Issue is pending triage label Oct 16, 2023
@jeremymtx
Copy link
Author

Odd. About 15 minutes later, it appears to be working now:

PS C:\Users\aghor\OneDrive\Documents\programming\aws\workshops\serverlessWebApp\jpm-event-planner> amplify status

Current Environment: dev

┌──────────┬─────────────────────┬───────────┬───────────────────┐
│ Category │ Resource name │ Operation │ Provider plugin │
├──────────┼─────────────────────┼───────────┼───────────────────┤
│ Auth │ userPoolGroups │ No Change │ awscloudformation │
├──────────┼─────────────────────┼───────────┼───────────────────┤
│ Auth │ jpmeventplannerAuth │ No Change │ awscloudformation │
├──────────┼─────────────────────┼───────────┼───────────────────┤
│ Api │ jpmeventplanner │ No Change │ awscloudformation │
├──────────┼─────────────────────┼───────────┼───────────────────┤
│ Storage │ EventImages │ No Change │ awscloudformation │
└──────────┴─────────────────────┴───────────┴───────────────────┘

GraphQL endpoint: https://rd7qngicx5cc3mun3sc2lpdn5e.appsync-api.us-east-1.amazonaws.com/graphql

GraphQL transformer version: 2

@ykethan
Copy link
Member

ykethan commented Oct 16, 2023

Hey @jeremymtx, the issue appears to be similar to #12863
From the issue moving the project from the OneDrive directory mitigates the issue.
could you try moving the project out of the OneDrive directory and re-run the commands? we can run amplify pull --appId <appId> --envName <envName> in a new directory outside OneDrive to pull the backend and test this.

@ykethan ykethan added platform Issues tied to the general CLI platform pending-response Issue is pending response from the issue author labels Oct 16, 2023
@jeremymtx
Copy link
Author

Hmm...I'm hesitant to do that at the moment for fear of breaking something. I'd like to finish the app first which shouldn't take more than another couple of days. As mentioned, the command worked after about 10-15 minutes and still works. We can close this issue for now, and if I run into it again, I'll re-open it (if that's possible) after trying a move off of OneDrive.

@github-actions github-actions bot removed the pending-response Issue is pending response from the issue author label Oct 16, 2023
@ykethan
Copy link
Member

ykethan commented Oct 17, 2023

@jeremymtx I understand, the amplify pull command should just pull your backend resource and should not modify your resources. But if you do run into issues with the amplify pull in a new directory, please do not hesitate in reaching out. Closing the issue for now.

@ykethan ykethan closed this as not planned Won't fix, can't repro, duplicate, stale Oct 17, 2023
@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
Labels
pending-triage Issue is pending triage platform Issues tied to the general CLI platform
Projects
None yet
Development

No branches or pull requests

2 participants