2021-01-21: Staging QA test suites failing due to 429 errors
Current Status
QA tests started failing because of gitlab-qa user being rate-limited. Adding the user to the rate-limit exclusion list solved the issue.
Timeline
Recent Events (available internally only):
- Deployments
- Feature Flag Changes
- Infrastructure Configurations
- GCP Events (e.g. host failure)
All times UTC.
2022-01-20
-
21:51
- first QA pipeline with 429 failures is starting
2022-01-21
-
01:59
- @ggillies notices that QA pipelines on agitlab-com
change unrelated to deployments are failing https://ops.gitlab.net/gitlab-com/gl-infra/k8s-workloads/gitlab-com/-/pipelines/998715 -
02:05
- @ggillies declares incident in Slack. -
02:25
- @ggillies disables feature flagrate_limit_gitlab_shell
on gstg and retries QA pipelines -
03:31
- @ggillies enables feature flagrate_limit_gitlab_shell
on gstg after disabling it proves to have no impact on the issue -
05:08
- @ggillies disable gstg-cny gitaly/praefect nodes (weight 0) and reruns tests to see if it improves things, it does not -
05:48
- @ggillies re-enables gstg-cny gitaly/praefect nodes -
08:36
- rack attack rate limiting exclusion MR forgitlab-qa
andgitlab-qa-bot
is merged: gitlab-com/gl-infra/k8s-workloads/gitlab-com!1476 (merged) -
09:00
- QA passes -
09:33
- Incident set to 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.
- ...
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)