gitlab-rake gitlab:doctor:secrets stalls for ~13 minutes between CI checks
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
The gitlab-rake gitlab:doctor:secrets command is experiencing significant performance issues, stalling for approximately 13 minutes between "CI:Runner failures: 0" and "CI:Build failures: 0" output lines.
Description
When running the gitlab-rake gitlab:doctor:secrets command, the process appears to hang for about 13 between when the command outputs "CI:Runner failures: 0" and "CI:Build failures: 0". Importantly, there are no failures found at any point, and this issue has existed for our last few updates (I believe 17.10 but could have been 17.9)
This extended delay significantly impacts operational tasks and troubleshooting workflows that rely on this command. Example: we run this command before and after every update as recommended - this adds almost 30 minutes of downtime to our upgrade flow.
Steps to reproduce
- Access a GitLab instance with sufficient permissions
- Run the command
gitlab-rake gitlab:doctor:secrets - Observe delay
Expected behavior
The command should execute all checks with reasonable performance and without significant delays between output lines.
Actual behavior
The command stalls for approximately 13 minutes between the "CI:Runner failures: 0" and "CI:Build failures: 0" output lines.
Environment
- GitLab version: 17.10 through 18.0
- Installation type: Omnibus package
written with AI assistance to while waiting for command to run