2024-10-10: graphql 500 errors on work item updates
Customer Impact
This incident is caused by a new foreign key. It affects operations such as updating milestones and editing due dates related to work items. Fortunately, the scope of the impact is minimal because the foreign key check fails under a combination of conditions.
Visualized customer impact, broken down by graphQL operations: https://log.gprd.gitlab.net/app/r/s/TDu58 List of impacted requests broken down by
Since it was introduced, we observed less than 20 impacted projects in the last 6 hours.
Current Status
We have completed the rollout into Production of gitlab-org/gitlab!168741 (merged) which removes a database foreign key that caused this incident. We are no longer seeing InvalidForeignKey errors on the logs for the GraphqlController and consider this IncidentResolved.
More information will be added as we investigate the issue. For customers believed to be affected by this incident, please subscribe to this issue or monitor our status page for further updates.
📚 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.