2024-04-13: Some push (remote) mirrors failing to sync
Customer Impact
2k projects had a failed mirror update.
Current Status
Waiting for gitlab-org/omnibus-gitlab!7539 (merged) to get deployed to production to fix a bad curl
version.
We can use the logs below to validate that it's fixed.
Summary
There was a regression in curl
, which is causing 500 errors on gitlay
from the RemoteMirror
RPC. git
worked around this issue in https://github.com/git/git/commit/324231174247c70e66908b78924908fbfcebed19 but it's still not realed. Our current fix is to revert the curl
version in gitlab-org/omnibus-gitlab!7539 (merged).
📚 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.
Security Note: If anything abnormal is found during the course of your investigation, please do not hesitate to contact security.