2024-10-13: Sidekiq concurrency limit middleware stuck in ResumeWorker

Customer Impact

None

Current Status

Concurrency queues are now at 0 for all affected workers:

Source

All three workers have been set to execute jobs without deferral. As the MR gitlab-org/gitlab!169050 (merged) has been merged and deployed we can consider this IncidentResolved

Previous Status

We deployed the revert (gitlab-org/gitlab!169050 (merged)) and are waiting to clean up the jobs that had concurrency set:

source

When they hit 0 we can remove the defered feature flag for these queue to run normally again:

1. /chatops run feature delete run_sidekiq_jobs_Security::ProcessScanResultPolicyWorker --ignore-feature-flag-consistency-check
2. /chatops run feature delete run_sidekiq_jobs_Security::ScanExecutionPolicies::CreatePipelineWorker --ignore-feature-flag-consistency-check
3. /chatops run feature delete run_sidekiq_jobs_Security::ScanResultPolicies::AddApproversToRulesWorker --ignore-feature-flag-consistency-check

source

📚 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.