Skip to content

Job is stuck in the pending state even a runner has been enabled for the project

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

Job is stuck in the pending state even a runner has been enabled for the project

Steps to reproduce

  1. Set up a specific (not a shared) runner with some tags (e.g. fpc, linux in my case)
  2. Disable (or do not enable) this runner for a project.
  3. Set up .gitlab-ci.yml for the project. Tag one of jobs to this specific runner by its tags (e.g.fpc, linux)
  4. Push a branch/run a pipeline for the branch.
  5. Open project pipelines. See a just run pipeline job is stuck in the pending state with the message
This job is stuck, because you don't have any active runners online with any of these tags assigned to them: fpc  linux  
Go to Runners page
  1. Follow Runners links (open Settings - CI/CD page for the project). Expand Runners settings. Enable the specific runner in Available specific runners section.
  2. Return to the stuck pipeline. It is still stuck (job is the pending state).

What is the current bug behavior?

Job tagged to a specific runner remains in the pending state after the specific runner has been enabled for a project.

What is the expected correct behavior?

Job tagged to a specific runner remains is run after the specific runner has been enabled for a project.

P.S. Pausing and unpausing the runner triggers the pending job to run.

Results of GitLab environment info

N/A (I have no access to the console)

GitLab Community Edition 10.6.2 gitlab-ce@3e3c05b848f5675be24e2edc9fe573b781fba1dd

GitLab Runner - was 10.4.0 then upgraded to 11.1.0

Results of GitLab application Check

N/A (I have no access to the console)

Edited by 🤖 GitLab Bot 🤖