-
Notifications
You must be signed in to change notification settings - Fork 324
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
Pre-Deploy error on Push to CDN #9757
Comments
Promoting this one to this cycle; thank you for reporting/capturing @rafaelromcar-parabol |
It happened again on v7.35.0. |
This can be reproduced locally by
but does not happen every time. It's the s3 client trying to push but getting a 520 response. |
Happens also on 3.588 (latest) |
It happens in the |
The 520 response comes from Cloudflare and the S3 client does not know how to deal with it, so it treats it as 'CLIENT_ERROR' which means it's not retry-able. I'm looking if implementing a custom retry policy could solve this. |
Happened again in production 😢 |
Issue - Bug
node --version
npm --version
rethinkdb --version
App version v7.31.0
Error experienced in Staging with data that might have not been consistent
Then, after trying to reproduce on Staging and failing to do so, I experienced it again in one of our PPMIs. This was the sequence:
I tried running pre-deploy again and no luck. The client has not complained about anything and it looks like they have been using AWS without any trouble so far. I could not reproduce on Staging or using an on-demand-env.
Acceptance Criteria (optional)
Pre-Deploy does not throw that error
Triage is performed to find the root cause of the bug, timeboxed to ~1 hour.
Estimated effort: 1 hour to triage. More if root cause is already identified.
The text was updated successfully, but these errors were encountered: