Closed Bug 1188520 Opened 10 years ago Closed 10 years ago

HTTP 500 returned when querying scheduler for non-existing taskgraphid

Categories

(Taskcluster Graveyard :: Scheduler, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: pmoore, Unassigned)

References

Details

E.g. https://tools.taskcluster.net/task-graph-inspector/#dtXuF2n9S-i83G37V9eBuO/ returns: 500: Internal Server Error { "message": "Internal Server Error", "error": { "info": "Ask administrator to lookup incidentId in log-file", "incidentId": "560ae4f4-3cc8-4f11-b3d4-dacb0c4dc661" } }
From papertrail: Jul 28 20:20:06 taskcluster-scheduler app/web.5: Tue, 28 Jul 2015 18:20:06 GMT base:api Error occurred handling: /v1/task-graph/dtXuF2n9S-i83G37V9eBuO/inspect, err: [object Object], as JSON: {"statusCode":404,"code":"ResourceNotFound","body":{"code":"ResourceNotFound","message":{"lang":"en-US","value":"The specified resource does not exist.\nRequestId:7afe5db7-0002-0087-4b62-c9aa25000000\nTime:2015-07-28T18:20:09.1810269Z"}},"retriesMade":0}, incidentId: 560ae4f4-3cc8-4f11-b3d4-dacb0c4dc661 undefined
Fixed and fix landed... I've been reluclant to fix anything in the task-graph-scheduler because we're eventually replacing it. But this was quick.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: Taskcluster → Taskcluster Graveyard
You need to log in before you can comment on or make changes to this bug.