2024-04-22: Creation of downstream pipelines fails
Customer Impact
There is growing number of pipeline creation failure for specific situation ( Pipeline created using the trigger token)
Current Status
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.
No service SLA threshold has been reached yet. We are seeing an increase of sidekick job failures for CreateDownstreamPipelineWorker

Summary for CMOC notice / Exec summary:

- Customer Impact: Creation of downstream pipeline fails in some circumstances with
data integrity failure
, forcing customers to alter their CI configuration to workaround the problem or retry the pipeline. - Service Impact: This is a development bug, no specific service is directly impacted.
- Impact Duration: 2024-04-19 13:53 UTC - 2024-04-23 13:43 UTC - (5750 mins)
- Root cause: Software change.

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.