2022-05-30: ReadTimeout errors on Quality deployment pipelines
Incident Roles
The DRI for this incident is the incident issue assignee, see roles and responsibilities.
Roles when the incident was declared:
Current Status: Incident mitigated
QA failures on the latest deployment to canary are failing with ReadTimeout
errors, the failure happens when Resource::PersonalAccessToken.fabricate
is called.
The failures were caused by gitlab-org/gitlab!84373 (diffs), after disabling the feature flag QA was green on canary again.
Summary for CMOC notice / Exec summary:
- Customer Impact: No customer impact
- Service Impact: ServiceGitLab Rails
- Impact Duration:
18:04
-21:51
(287 minutes) - Root cause: RootCauseFeature-Flag
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-05-30
-
18:04
- QA main and smoke start failing on canary -
18:36
- @richard.chong points out it could be related to gitlab-org/gitlab#362980 (closed) -
19:38
- Multiple retries are performed with the same result -
19:45
- @richard.chong reaches out to Engineering Productivity -
20:57
- @a_mcdonald points out it could be a different issue associated with personal access tokens gitlab-org/gitlab#363809 (closed) -
21:06
- @mayra-cabrera declares incident in Slack. -
21:38
- @nnelson disablesaccess_token_ajax
-
21:51
- QA is green again on canary
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.
- Update script for removing test PATs and add a cleanup job
- Revisit tests that force create new PATs for default user to see if
GITLAB_QA_ACCESS_TOKEN
can be used
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)