2020-10-15: Unable to upload Maven packages due to Rack (ruby gem) upgrade
Summary
Unable to upload Maven packages due to a Rack upgrade
This is Rack (Link)
See gitlab-org/gitlab#267598 (closed)
This is causing all Maven uploads to fail
https://log.gprd.gitlab.net/goto/abf0a0b75d23401558efc87d237d15c6
Timeline
All times UTC.
2020-10-15
- 08:23 - jarv declares incident in Slack using
/incident declare
command.
Corrective Actions
- Rack attack upgrade reverted in gitlab-org/gitlab!45246 (merged)
- Add a missing test for uploading Maven packages gitlab-com/www-gitlab-com#9331 (closed)
- Add Gradle coverage for deploying a Maven package gitlab-org/gitlab!45461 (merged)
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 John Jarvis