2020-08-19: post-deploy migration failure on staging
Summary
post-deploy migration failure on staging
Staging deploys are blocked due to a post-deploy migration failure.
20200811130433_create_missing_vulnerabilities_issue_links
MR: gitlab-org/gitlab!39098 (merged)
job: https://ops.gitlab.net/gitlab-com/gl-infra/deployer/-/jobs/1648700
Revert MR: gitlab-org/gitlab!39813 (merged)
Timeline
All times UTC.
2020-08-19
- 08:57 - jarv declares incident in Slack using
/incident declare
command.
Click to expand or collapse the Incident Review section.
Incident Review
Summary
- Service(s) affected:
- Team attribution:
- 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 potential impact?
Incident Response Analysis
- How was the event detected?
- How could detection time be improved?
- How did we reach the point where we knew how to mitigate the impact?
- How could time to mitigation be improved?
Post Incident Analysis
- How was the root cause diagnosed?
- How could time to diagnosis be improved?
- Do we have an existing backlog item 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, have you linked the issue which represents the change?)?
5 Whys
Lessons Learned
Corrective Actions
Guidelines
Edited by Brent Newton