2023-09-22: Error rate increase in web
Customer Impact
A single bot/user requesting malformed URLs getting 500 errors
Current Status
A single user/bot is requesting malformed URLs like /gitlab-org/ci-cd/distribution/runner/self-hosted/-/commit/e4a90e6905b15c5d107bcfa285bcf2a8e17d780a?id=;</script><script>8tMU(9355)</script>
which ends triggering a 500 error in workhorse with no error.
Next steps:
-
Remove the rate limit added in https://ops.gitlab.net/gitlab-com/gl-infra/config-mgmt/-/merge_requests/6805 👉 https://ops.gitlab.net/gitlab-com/gl-infra/config-mgmt/-/merge_requests/6816 -
Revert Puma and deploy it to production 👉 gitlab-org/gitlab!132552 (merged) -
Expire silence 👉 https://alerts.gitlab.net/#/silences/33c62a94-03c1-43db-919b-18d481e3efd6 -
Check if we should cleanup some cloudflare firewall rules 👉 #16417 (comment 1577617859)
📚 References and helpful links
Recent Events (available internally only):
- Feature Flag Log - Chatops to toggle Feature Flags Documentation
- Infrastructure Configurations
- GCP Events (e.g. host failure)
Deployment Guidance
- Deployments Log | Gitlab.com Latest Updates
- Reach out to Release Managers for S1/S2 incidents to discuss Rollbacks, Hot Patching or speeding up deployments. | Rollback Runbook | Hot Patch Runbook
Use the following links to create related issues to this incident if additional work needs to be completed after it is resolved:
- Corrective action ❙ Infradev
- Incident Review ❙ Infra investigation followup
- Confidential Support contact ❙ QA investigation
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 our 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.