2020-05-14: Degraded performance on shared CI runners

Summary

Degraded performance on shared CI runners. Jobs might take a long time to start up.

Timeline

All times UTC.

2020-05-15

• 11:12 - Incident declared by t4cc0re in Slack via /incident declare command.
• 13:30 - Decision to shift shared-runners-manager-3 and 5 to use alternate A-Z
• 14:20 - shared-runners-manager-3 starts to use us-east-1c, still waiting on jobs for manager-5 to finish in 1d before it can shift

Click to expand or collapse the Incident Review section.

Incident Review

1. Service(s) affected :
2. Team attribution :
3. Minutes downtime or degradation :

Metrics

Customer Impact

1. Who was impacted by this incident? (i.e. external customers, internal customers)
2. What was the customer experience during the incident? (i.e. preventing them from doing X, incorrect display of Y, ...)
3. How many customers were affected?
4. If a precise customer impact number is unknown, what is the estimated potential impact?

Incident Response Analysis

1. How was the event detected?
2. How could detection time be improved?
3. How did we reach the point where we knew how to mitigate the impact?
4. How could time to mitigation be improved?

Post Incident Analysis

1. How was the root cause diagnosed?
2. How could time to diagnosis be improved?
3. Do we have an existing backlog item that would've prevented or greatly reduced the impact of this incident?
4. Was this incident triggered by a change (deployment of code or change to infrastructure. if yes, have you linked the issue which represents the change?)?

Timeline

• YYYY-MM-DD XX:YY UTC: action X taken
• YYYY-MM-DD XX:YY UTC: action Y taken

5 Whys

Lessons Learned

Corrective Actions

Guidelines

• Blameless RCA Guideline

Resources

1. If the Situation Zoom room was utilised, recording will be automatically uploaded to Incident room Google Drive folder (private)