2022-03-11: SSL certificate problem with shared runners & submodules
Incident DRI
Current Status
Impact of this incident has been mitigated. If you are still experiencing problems please reach out to GitLab Support
Customers utilizing GitLab.com shared runners encountered issues with submodules unable to clone HTTPS repo endpoints due to certificate errors.
This issue was related to a change executed in the last day. This change has been reverted in the green shared ci runner environment and all new jobs have been shifted to run on green.
Related investigation issue for follow-up after the incident: https://gitlab.com/gitlab-com/gl-infra/reliability/-/issues/15415
Summary for CMOC notice / Exec summary:
- Customer Impact: Some shared runner jobs are failing when attempting https clone
- Service Impact: ServiceCI Runners
- Impact Duration: Mar 10, 1530 UTC - Mar 11, 0530 UTC ( 14 hours duration )
- Root cause: RootCauseConfig-Change
Timeline
Recent Events (available internally only):
- Deployments
- Feature Flag Changes
- Infrastructure Configurations
- GCP Events (e.g. host failure)
- Gitlab.com Latest Updates
All times UTC.
2022-03-10
-
1530
- change to shared runner CI environment to add proxy implemented issue 14874 (internal only)
2022-03-11
-
0230
- @kenneth declares incident in Slack as a result of multiple customer ticket submissions. -
0300
- EOC identifies the earlier change to likely be the cause of this impact -
0315
- escalated to devoncall to have assistance in reproducing the problem -
0340
- escalate to additional SRE for assistance with both reproduction of the problem and to find log/event sources -
0435
- revert completed in the green environment, now shifting to have all new jobs go to green -
0530
- green environment jobs all drained (except less than 20 long running jobs). No new indications of problems, moving incident status to mitigated.
Create related issues
Use the following links to create related issues to this incident if additional work needs to be completed after it is resolved:
Takeaways
- ...
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.
- corrective actions may come out of the investigation issue https://gitlab.com/gitlab-com/gl-infra/reliability/-/issues/15415
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)