2024-07-09: AI related E2E tests failing in staging
Customer Impact
None: this is only impacting staging at this point in time.
Current Status
We've started to see a number of test failures related to GitLab Duo. It appears to be unavailable in the staging environment and we're seeing errors in both GitLab Duo Chat and in Code Suggestions via the WebIDE.
- https://gitlab.com/gitlab-org/gitlab/-/issues/471565
- https://gitlab.com/gitlab-org/gitlab/-/issues/471564
These tests are part of the smoke suite so will block deployments
Failure Messages visible in the UI via Duo Chat: I'm sorry, I can't generate a response. Please try again. Error code: A1001
This is because in chore(runway): use staging vertex project for t... (gitlab-org/modelops/applied-ml/code-suggestions/ai-assist!1014 - merged) we updated the vertex project which resulted into it being unavailable. This was fixed by reverting the original merge request. The pipeline on main
branch failed so we should have caught this, and as a corrective action we are implementing Send a Slack message when a `main` pipeline fails (gitlab-org/modelops/applied-ml/code-suggestions/ai-assist#547) and Request to 3rd model providers in integration t... (gitlab-org/modelops/applied-ml/code-suggestions/ai-assist#546)
📚 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.