2022-01-13 Users unable to access files via UI on nfs-file19
Current Status
A specific Gitaly server was unexpectedly rebooted, which caused a small amount of Git repos on that machine to become corrupt
Timeline
Recent Events (available internally only):
- Deployments
- Feature Flag Changes
- Infrastructure Configurations
- GCP Events (e.g. host failure)
All times UTC.
2022-01-13
-
01:03
- Gitaly node nfs-file19 experiences an underlying GCP failure and terminates uncleanly -
01:13
- Gitaly node nfs-file19 is restarted by GCP and is back online -
23:35
- @lbot declares incident in Slack.
2022-01-14
-
00:10
- @proglottis and @stanhu joins the call -
00:37
- @stanhu fixes the first customer reported corrupt repository usinggit update-ref
-
00:47
- @stanhu fixes the second customer reported corrupt repository usinggit update-ref
(Note: themaster
branch of this repo had to be pushed back. We think this can be fixed by the customer using the data from a merge request). -
00:58
- @stanhu fixes the third corrupt repository (found via https://log.gprd.gitlab.net/goto/823db160-74d5-11ec-a649-b7cbb8e4f62e) usinggit update-ref
-
01:19
- @ggillies marks the incident as IncidentMitigated as agreed on the call.
Takeaways
- ...
Corrective Actions
- Enable fsync for git - gitlab-org/gitaly#3998 (closed)
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.
- ...
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.
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
-
Who was impacted by this incident? (i.e. external customers, internal customers)
- ...
-
What was the customer experience during the incident? (i.e. preventing them from doing X, incorrect display of Y, ...)
- ...
-
How many customers were affected?
- ...
-
If a precise customer impact number is unknown, what is the estimated impact (number and ratio of failed requests, amount of traffic drop, ...)?
- ...
What were the root causes?
- ...
Incident Response Analysis
-
How was the incident detected?
- ...
-
How could detection time be improved?
- ...
-
How was the root cause diagnosed?
- ...
-
How could time to diagnosis be improved?
- ...
-
How did we reach the point where we knew how to mitigate the impact?
- ...
-
How could time to mitigation be improved?
- ...
-
What went well?
- ...
Post Incident Analysis
-
Did we have other events in the past with the same root cause?
- ...
-
Do we have existing backlog items that would've prevented or greatly reduced the impact of this incident?
- ...
-
Was this incident triggered by a change (deployment of code or change to infrastructure)? If yes, link the issue.
- ...
What went well?
- ...
Guidelines
Resources
- If the Situation Zoom room was utilised, recording will be automatically uploaded to Incident room Google Drive folder (private)