Closed Bug 1453676 Opened 8 years ago Closed 7 years ago

Unknown 400 errors from AWS

Categories

(Taskcluster :: Services, defect, P4)

Product:
Taskcluster
Component:
Services
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: dustin, Unassigned)

Details

https://sentry.prod.mozaws.net/operations/taskcluster-auth/issues/3189005/ Auth is getting a bunch of these today (and has seen them in the past). Looking at the code that generates the JS error object, I *think* this comes from a 400 response with no body, no `x-amzn-errortype`, and no message after the "400" in the first line. So basically, something at Amazon is failing badly. Probably nothing to worry about until it occurs enough to start causing issues, at which point it might be useful to monkey-patch require('aws-sdk/lib/protocol/json').extractError to include more useful information in the exception.
Priority: -- → P4
Status: NEW → RESOLVED
Closed: 7 years ago
QA Contact: dustin
Resolution: --- → WORKSFORME
Component: Authentication → Services
You need to log in before you can comment on or make changes to this bug.