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

Suddenly seeing 500's after re-deploying known working revisions #3793

Closed
5 tasks done
iamcgn opened this issue Nov 7, 2023 · 4 comments
Closed
5 tasks done

Suddenly seeing 500's after re-deploying known working revisions #3793

iamcgn opened this issue Nov 7, 2023 · 4 comments
Assignees
Labels
archived This issue has been locked. compute duplicate

Comments

@iamcgn
Copy link

iamcgn commented Nov 7, 2023

Before opening, please confirm:

  • I have checked to see if my question is addressed in the FAQ.
  • I have searched for duplicate or closed issues.
  • I have read the guide for submitting bug reports.
  • 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.

App Id

d3r3cld460f6i7

AWS Region

us-east-2

Amplify Hosting feature

SSR

Frontend framework

Next.js

Next.js version

13.5.5

Next.js router

Pages Router

Describe the bug

After deploying a seemingly innocuous change to my dev environment I started getting 500's. Redeploying old versions that we were previously working does not resolve the issue. The error in the compute logs show a readonly filesystem error:

ln: failed to create symbolic link ‘/tmp/app/amplify-compute-bundle-output/amplify-compute-bundle-output’: Read-only file system

Expected behavior

I expect to be able to deploy updates and/or revert to previous versions.

Reproduction steps

  1. Deploy anything
  2. Notice a 500 response with readonly filesystem errors in the log.

Build Settings

No response

Log output

# Put your logs below this line
ln: failed to create symbolic link ‘/tmp/app/amplify-compute-bundle-output/amplify-compute-bundle-output’: Read-only file system

Additional information

No response

@iamcgn
Copy link
Author

iamcgn commented Nov 7, 2023

Looks like this issue was opened while I was writing mine. This appears to be the same issue: #3792

@Jay2113
Copy link
Contributor

Jay2113 commented Nov 7, 2023

Hi @iamcgn 👋 , thanks for raising this and apologies for the inconvenience caused due to this issue.

I am going to close this thread in favor of #3792 . Please track and monitor it for any further updates on the issue.

@Jay2113 Jay2113 closed this as not planned Won't fix, can't repro, duplicate, stale Nov 7, 2023
Copy link

github-actions bot commented Nov 7, 2023

⚠️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.

Copy link

github-actions bot commented Nov 7, 2023

This issue has been automatically locked.

@github-actions github-actions bot added the archived This issue has been locked. label Nov 7, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Nov 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
archived This issue has been locked. compute duplicate
Projects
None yet
Development

No branches or pull requests

2 participants