Closed Bug 1269627 Opened 8 years ago Closed 8 years ago

Firefox-47.0b2-build1 started even though we get 503 submitting the task graph

Categories

(Release Engineering :: Release Automation: Other, defect)

Product:
Release Engineering
Component:
Release Automation: Other
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: nthomas, Unassigned)

References

Details

2016-05-02 20:01:36,225 - DEBUG - "PUT /v1/task-graph/ecs5DuTnSWyp-LC-i4YHRQ HTTP/1.1" 503 484
2016-05-02 20:01:36,228 - DEBUG - Received HTTP Status:  503
2016-05-02 20:01:36,228 - DEBUG - Received HTTP Headers: {'content-length': '484', 'server': 'Cowboy', 'connection': 'keep-alive', 'cache-control': 'no-cache, no-store', 'date': 'Tue, 03 May 2016 03:01:35 GMT', 'content-type': 'text/html; charset=utf-8'}
2016-05-02 20:01:36,228 - DEBUG - Received HTTP Payload: <!DOCTYPE html>
    <html>
    <head>
      <meta name="viewport" content="width=device-width, initial-scale=1">
      <style type="text/css">
        html, body, iframe { margin: 0; padding: 0; height: 100%; }
        iframe { display: block; width: 100%; border: none; }
      </style>
    <title>Application Error</title>
    </head>
    <body>
      <iframe src="//s3.amazonaws.com/heroku_pages/error.html">
        <p>Application Error</p>
      </iframe>
    </body>
    </html> (limit 1024 char)
2016-05-02 20:01:36,228 - WARNING - Retrying because of: 503 Server Error: Service Unavailable
2016-05-02 20:01:36,228 - INFO - Sleeping 0.10 seconds for exponential backoff

Failed all retries, and marked the release failed in ship-it, but the graph is active:
 https://tools.taskcluster.net/task-group-inspector/#ecs5DuTnSWyp-LC-i4YHRQ/

Please investigate!
In bug 1259599 we added a guard to prevent release runner submitting the same graph with different graphId multiple times. (it's ok to submit the same graph with the same grapId, it won't hurt).

The real solution would be implementing bug 1259627.
Assignee: rail → nobody
See Also: → 1259599
Ok, so is this 'return a 503 but actually work' a known thing the tc scheduler. Since the graph did start we are OK for this release.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
See Also: → 1332247
You need to log in before you can comment on or make changes to this bug.