Closed
Bug 1201142
Opened 9 years ago
Closed 9 years ago
All trees closed due to Taskcluster 503 errors burning all builds
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: RyanVM, Unassigned)
References
Details
No description provided.
Comment 1•9 years ago
|
||
queue was restarted at around 17:07Z and errors stopped. So far Jonas has noticed issues with communication between various taskcluster components and Pulse starting around 16:23Z.
Comment 2•9 years ago
|
||
From consulting :cyliang, looks like we've got a network issue between AWS and PHX1, dropping packets at a high % inside Telia routing space. New Relic traffic is another service also affected.
Comment 3•9 years ago
|
||
At 10:15am PT, netops turned off the circuit to that provide to stop the packet hemorrhage.
Reporter | ||
Comment 4•9 years ago
|
||
Bustage has been cleared, trees reopened.
Reporter | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•