2021-03-29: QA in staging is failing, blocking staging deploys
Current Status
Deployments to staging are failing, as a result of QA jobs timing out after one hour:
- https://ops.gitlab.net/gitlab-com/gl-infra/deployer/-/jobs/3490562
- https://ops.gitlab.net/gitlab-org/quality/staging/-/pipelines/533347
Per Slack, this is a persistent issue: https://gitlab.slack.com/archives/C3JJET4Q6/p1617005361127900
More information will be added as we investigate the issue.
Summary for CMOC notice / Exec summary:
- Customer Impact: Services Impacted
- Customer Impact Duration: start time UTC - end time UTC ( duration in minutes )
- Current state: See
Incident::<state>
label - Root cause: TBD
Timeline
View recent production deployment and configuration events (internal only)
All times UTC.
2021-03-29
-
08:19
- @yorickpeterse declares incident in Slack. -
09:10
- @willmeek asks in#wg_feature_flag-usage
about the errors they found in Sentry -
09:48
- @yorickpeterse asks @amyphillips to escalate the incident -
10:23
- @yorickpeterse asks @brentnewton if they know who to escalate the message in#wg_feature_flag-usage
to -
10:30
- @yorickpeterse escalates the incident using the dev escalation protocol -
10:36
- @cwiesner starts looking into the dev escalation -
12:26
- @ayufan shares what they believe to be the cause of the incident: #4091 (comment 540067804) -
12:44
- a revert merge request is set up: #4091 (comment 540093535) -
14:59
- the revert merge request is merged: #4091 (comment 540223619) -
20:59
- the incident is marked as resolved: #4091 (comment 540450461)
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.
- gitlab-org/gitlab#326281
- Extra tests around
gitaly
feature flags gitlab-org/gitlab#326724
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
Summary
- Service(s) affected:
- Team attribution:
- Time to detection:
- Minutes downtime or degradation:
Metrics
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)