2022-02-02: Firing 1 - Containers for the `git` service, `main` are unable to unable to start.

Incident DRI

@rehab

Current Status

Non-user impacting alert, this occurred during a deployment (obviously), upon observing the state and logs of the pods involved, we quickly concluded that this incident's cause is RootCauseIndeterminate , we don't manage calico pods, and errors related to them are usually of unknown reasons to us.

A low priority corrective action will be created to investigate this issue, especially given that it self-recovered.

Alert's description for reference:

More than 50% of the deployment's maxSurge setting consists of containers unable to start for reasons other than ContainerCreating.

Timeline

Recent Events (available internally only):

• Deployments
• Feature Flag Changes
• Infrastructure Configurations
• GCP Events (e.g. host failure)

All times UTC.

2022-02-02

• 13:38 - Alert fired.
• 13:49 - @rehab declares incident in Slack.
• 13:56 - Alert self-cleared.

Takeaways

• These git pods reside only in zonal clusters.
• The Runbook link to this Alert was non-extent leaving EOC in a lot of question marks.

Corrective Actions

Corrective actions should be put here as soon as an incident is mitigated, ensure that all corrective actions mentioned in the notes below are included.

• Investigate Calico connectivity issues during deployments https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/15128

---

Note: In some cases we need to redact information from public view. We only do this in a limited number of documented cases. This might include the summary, timeline or any other bits of information, laid out in out handbook page. Any of this confidential data will be in a linked issue, only visible internally. By default, all information we can share, will be public, in accordance to our transparency value.

Create a confidential issue

Click to expand or collapse the Incident Review section.

Incident Review

• Ensure that the exec summary is completed at the top of the incident issue, the timeline is updated and relevant graphs are included in the summary
• If there are any corrective action items mentioned in the notes on the incident, ensure they are listed in the "Corrective Action" section
• Fill out relevant sections below or link to the meeting review notes that cover these topics

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?

• ...

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. ...

What went well?

• ...

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)