2025-01-17: GitLab Duo Root Cause Analysis feature is not working on gitlab.com

Customer Impact

Customers can not use "Troubleshoot" feature on gitlab.com since 2024-01-17 07:30 UTC.

2025-01-17_19-16

Current Status

We are waiting for gitlab-org/gitlab!178279 (merged) to be deployed to production. After that is done we should the errors below drop to 0

image

source

📚 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.

Edited Jan 18, 2025 by Steve Xuereb
Assignee Loading
Time tracking Loading