Skip to content

Update file job_artifacts_troubleshooting.md

Michelle Almendarez requested to merge add_reason_for_feature_flag_ into master

What does this MR do and why?

New feature flag was added due to Issue 435051 as well as a separate customer ticket Zendesk #481266 to combat issue with pipelines becoming stuck after upgrade to 16.5+

It appears due to feature addition !124112 (merged) defaults were increased in !133459 (merged)

Setting the variable MAX_RUNNING_LOW = 50 where the old default was 5. See changes

The default of 50 max concurrent running workers for unlocking pipelines can be too much for small self-managed instances.

This can cause some pipelines to get stuck with ci_unlock_pipelines error after an upgrade. The feature flag ci_unlock_pipelines_extra_low lowers this value for customers who run into this issue.

Chat with ops can also be found here https://gitlab.slack.com/archives/CPANF553J/p1703029028622189

MR for new feature flag !140318 (merged)

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Michelle Almendarez

Merge request reports