2024-06-25: staging smoke tests failing - 500 on Gitaly repository storage
Customer Impact
N/A
Current Status
-
Failing job: https://ops.gitlab.net/gitlab-org/quality/staging/-/jobs/14425757
-
Blocked deployment pipeline: https://ops.gitlab.net/gitlab-org/release/tools/-/pipelines/3437392
-
We recently deployed an update to the gitaly version gitlab-org/gitlab!157281 (diffs), so we're reverting that with gitlab-org/gitlab!157343 (merged)
-
Logs suggest a certificate was not found
-
gitlab-org/gitaly!6941 (merged) touched
*ReceivePack
RPCs recently, and seems to have been recently deployed on staging-canary -
gitlab-org/gitaly!7040 (merged) as potential fix
- the
components:update_gitaly
schedule has been paused for now until it is merged.
- the
-
Re-occurred today, as the gitaly repo has diverged due to the patch release
-
It's being resolved now that the patch release is out, and the repositories are back in sync.
- gitlab-org/gitlab!157512 (merged) will update the gitaly version on gitlab to the expected one.
📚 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.