<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary <!-- Summarize the bug encountered concisely. --> We have observed unreliable connection for some time when trying to restart runner after updating `config.toml` file. ### Steps to reproduce <!-- Describe how one can reproduce the issue - this is very important. Please use an ordered list. --> 1. Install runner in docker container and [register](https://gitlab.com/gitlab-org/gitlab/-/blob/master/qa/qa/service/docker_run/gitlab_runner.rb?ref_type=heads#L37-53) to a test project. 2. [Update runner's policy](https://gitlab.com/gitlab-org/gitlab/-/blob/master/qa/qa/specs/features/browser_ui/4_verify/pipeline/pipeline_with_image_pull_policy_spec.rb?ref_type=heads#L105-123) in `config.toml` 3. [Restart](https://gitlab.com/gitlab-org/gitlab/-/blob/master/qa/qa/resource/user_runners.rb?ref_type=heads#L83-87) container and wait for runner to be back online. ### Example Project <!-- If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report. If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version. --> ### What is the current *bug* behavior? <!-- Describe what actually happens. --> Runners at times just wouldn't come back online. ### What is the expected *correct* behavior? <!-- Describe what you should see instead. --> Should come back online within 60 seconds. ### Relevant logs and/or screenshots <!-- Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise. --> See failure issues: - https://gitlab.com/gitlab-org/gitlab/-/issues/461290 - https://gitlab.com/gitlab-org/gitlab/-/issues/498988 - https://gitlab.com/gitlab-org/gitlab/-/issues/504929 - https://gitlab.com/gitlab-org/gitlab/-/issues/504943 ### Output of checks <!-- If you are reporting a bug on GitLab.com, uncomment below --> <!-- This bug happens on GitLab.com --> <!-- and uncomment below if you have /label privileges --> <!-- /label gitlab~3293941 --> <!-- or follow up with an issue comment of `@gitlab-bot label gitlab~3293941` if you do not --> #### Results of GitLab environment info <!-- Input any relevant GitLab environment information if needed. --> <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`) </pre> </details> #### Results of GitLab application Check <!-- Input any relevant GitLab application check information if needed. --> <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:check SANITIZE=true`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`) (we will only investigate if the tests are passing) </pre> </details> ### Possible fixes <!-- If you can, link to the line of code that might be responsible for the problem. --> <!-- If you don't have /label privileges, follow up with an issue comment of `@gitlab-bot label gitlab~2278648` -->