2024-02-15: Failing E2E Test cancel_pipeline_when_block_user_spec in Staging Canary
Customer Impact
None - this was declared as backstage incident to block the deploy from proceeding to production. The failing test did indicate a valid problem with the package that would have proceeded to production. A revert of the problematic code was done and the production auto-deploys were unblocked once we verified tests were passing.
Current Status
Production deploys unblocked.
📝 Summary for CMOC notice / Exec summary:
- Customer Impact: None
- Service Impact: Production deploys blocked
-
- Impact Duration: start time UTC - end time UTC ( duration in minutes )
- Root cause: TBD
📚 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.