2022-12-15: Intermittent 500 when visiting QA group on production canary

Current Status

Intermittent timeouts resulting in 500 errors on several pages were identified. This appears related to a recent change to an existing feature. Issue confirmed through QA test job.

• The relevant feature flag ban_user_feature_flag was disabled
• QA testing internal link
• A revert MR was merged gitlab-org/gitlab!107038 (merged)
• The feature flag ban_user_feature_flag was re-enabled (as this affects more areas of the application than the revert covered)

Note a prior concern with the performance of this feature gitlab-org/gitlab#383552 (closed) won't be resolved by the revert.

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 and/or Hot Patching | 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 out 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.