2021-10-26: Repository mirror update delays
Current Status
Update: See here for the root cause.
Within the last 6 hours we've seen a spike in overdue mirror update delays, which resulted in at least one customer emergency.
Last 6 hours:
Timeline
Recent Events (available internally only):
- Deployments
- Feature Flag Changes
- Infrastructure Configurations
- GCP Events (e.g. host failure)
All times UTC.
2021-10-26
-
21:28
- Support customer emergency oncall reached out to larger support team for investigating customer emergency in Slack. -
21:45
- Support team members determined there was a large spike in overdue mirrors around the same time as customer's issue. Due to repeated recent stuck mirror updates, S3 incident declared due to concerns of larger, ongoing issue. -
21:55
- @tristan declares incident in Slack. -
22:20
- Console commands were run to manually fail the customer's repo mirror import state. Unfortunately, this did not trigger an update as it should have. See https://gitlab.com/gitlab-com/support/internal-requests/-/issues/10403 for commands run -
22:25
- Dev escalation to help determine how to manually trigger an update. -
23:08
- Stan ran update worker manually to trigger a mirror update. -
23:09
- Support team members confirmed that customer's mirror was updated successfully. -
23:40
- Support team members confirmed next customer's mirror update was successful.
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.
- ...
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.
- ...
Lessons Learned
- ...
Guidelines
Resources
- If the Situation Zoom room was utilised, recording will be automatically uploaded to Incident room Google Drive folder (private)