2021-03-24: The mimemagic Gem has been yanked, and re-released under the GPL; preventing any deploys or releases
Current Status
This is tracked in gitlab-org/gitlab#325838 (closed). The incident here exists for added visibility, and as this problem blocks us from deploying and possibly releasing any new version of GitLab.
Summary for CMOC notice / Exec summary:
- Customer Impact: No customer impact
- Customer Impact Duration: none
- Current state: IncidentResolved
- Root cause: A public gem was removed due to license violation gitlab-org/gitlab#325838 (closed), affecting the wider Rails community in the process https://github.com/rails/rails/issues/41750 .
Timeline
View recent production deployment and configuration events (internal only)
All times UTC.
2021-03-24
-
14:00
- @yorickpeterse declares incident in Slack. -
14:15
- @marin raises the severity to S1 due to an impact on GitLab.com capability to deploy, and GitLab capability to provide a release to our self-managed customers -
14:59
- In the incident call, next steps are decided to unblock .com #4054 (comment 536776940) -
16:56
- Our deployment pipelines are unblocked and the next steps are noted per #4054 (comment 53704693)
2021-03-25
-
05:53
- all but one of the MRs needed to resolve the issue have been merged. The pipeline for the last MR is running and, if thepackage-and-qa
job passes, we'll merge. -
09:18
- There is one more MR to merge, gitlab-org/gitlab!57443 (merged) before we can mark this incident as mitigated and resume deploys -
13:34
- We are still blocked on deployments, we added a workaround in gitlab-org/ruby-magic!5 (merged) and switched to the forked version in gitlab-org/gitlab!57487 (merged). Once we confirm we are unblocked with the workaround, we will transition to IncidentMitigated -
14:52
- gitlab-org/gitlab!57487 (merged) is merged, creating a new auto-deploy branch at the moment. Once created, we need to once again wait for the tests to pass. -
22:49
-@tkuah
opened #4069 (moved) to keep track of required backports #4069 (moved)
2021-03-26
-
01:59
- production deployed finished (13.11.202103251921-21c61a183b9.305e3b3e679)
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 action Increase resiliency to external events gitlab-org/distribution/team-tasks#225 (closed)
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)