2020-12-11 Multiple failures during Production deployment

Summary

https://ops.gitlab.net/gitlab-com/gl-infra/deployer/-/pipelines/378892 failing with errors on Git, Sidekiq, Web, and API

The combination of k8s-workloads, tanka-deployment and deployment was causing contention on the release runner. The release runner is a single 8 core VM that is currently over-utilized.

As a corrective action we are going to allocate more runner resources, tracked in https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/12134

Timeline

All times UTC.

2020-12-11

11:10 - aphillips declares incident in Slack.

Corrective Actions

• Add more runner resource https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/12134
• Separate out non-critical workloads from release runner https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/12138

---

Click to expand or collapse the Incident Review section.

Incident Review

---

Summary

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

Metrics

Customer Impact

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

What were the root causes?

"5 Whys"

Incident Response Analysis

1. How was the incident detected?
   1. ...
2. How could detection time be improved?
   1. ...
3. How was the root cause diagnosed?
   1. ...
4. How could time to diagnosis be improved?
   1. ...
5. How did we reach the point where we knew how to mitigate the impact?
   1. ...
6. How could time to mitigation be improved?
   1. ...
7. What went well?
   1. ...

Post Incident Analysis

1. Did we have other events in the past with the same root cause?
   1. ...
2. Do we have existing backlog items that would've prevented or greatly reduced the impact of this incident?
   1. ...
3. Was this incident triggered by a change (deployment of code or change to infrastructure)? If yes, link the issue.
   1. ...

Lessons Learned

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)

Incident Review Stakeholders