Details
-
Bug
-
Status: Open (View Workflow)
-
Blocker
-
Resolution: Unresolved
-
Jenkins 2.222.1
throttle-concurrents 2.0.2
Debian GNU/Linux 10.3 amd64
Java 11.0.6+10-post-Debian-1deb10u1
Description
I "apt dist-upgrade"-d my build Jenkins server, and was updated from 2.204.4 to 2.222.1, and now I am running into issues.
The major issue is that my throttled builds do not work. I have a build (see attached creenshot)
that is configured with throttling:
<hudson.plugins.throttleconcurrents.ThrottleJobProperty plugin="throttle-concurrents@2.0.2">
<maxConcurrentPerNode>1</maxConcurrentPerNode>
<maxConcurrentTotal>1</maxConcurrentTotal>
<categories class="java.util.concurrent.CopyOnWriteArrayList">
<string>vm-installer</string>
<string>kickstart-repo</string>
</categories>
<throttleEnabled>true</throttleEnabled>
<throttleOption>category</throttleOption>
<limitOneJobWithMatchingParams>true</limitOneJobWithMatchingParams>
<matrixOptions>
<throttleMatrixBuilds>false</throttleMatrixBuilds>
<throttleMatrixConfigurations>true</throttleMatrixConfigurations>
</matrixOptions>
<paramsToUseForLimit></paramsToUseForLimit>
<configVersion>1</configVersion>
</hudson.plugins.throttleconcurrents.ThrottleJobProperty>
It is set up to build on a single node:
<hudson.matrix.LabelAxis>
<name>label</name>
<values>
<string>kickstartbuild</string>
</values>
</hudson.matrix.LabelAxis>
The pop-up says that is waiting for the next available executor, which is "master", which is the only one satisfying this label. It is idle, but Jenkins is still waiting.
The configuration worked fine before upgrading. Restarting Jenkins does not help.
Attachments
Activity
Chris McAfee
added a comment - - edited We are seeing this problem on LTS 2.222.4
oleg_nenashev , can you take a look at this one? 
Peter Krefting
added a comment - Any news on this?
I have pinned Jenkins to 2.204.6 on our sever to be able to use it, but it is increasingly complaining about unfixed vulnerabilities.
Peter Krefting
added a comment - Any news on this?
I have pinned Jenkins to 2.204.6 on our sever to be able to use it, but it is increasingly complaining about unfixed vulnerabilities. Peter Krefting
added a comment - The problem persists in the current version (2.289.3), when I try to start a tied job manually after upgrading to this version, it blocks in "Waiting for next available executor on 'master'" despite no other jobs being active across the system.
Peter Krefting
added a comment - The problem persists in the current version (2.289.3), when I try to start a tied job manually after upgrading to this version, it blocks in "Waiting for next available executor on 'master'" despite no other jobs being active across the system. 
Valentin Maechler
added a comment - What's the status of this issue?
We tried to use the Job-Restriction plugin to allow only a certain job on master. But that also blocks the execution of other jobs even though they are actually not executed on the master but (always) on slaves.
For these "slave jobs" it says in the build queue: "(pending—Waiting for next available executor on ‘master’)".
So it looks to be caused by this issue.
Valentin Maechler
added a comment - What's the status of this issue?
We tried to use the Job-Restriction plugin to allow only a certain job on master. But that also blocks the execution of other jobs even though they are actually not executed on the master but (always) on slaves.
For these "slave jobs" it says in the build queue: "(pending—Waiting for next available executor on ‘master’)".
So it looks to be caused by this issue. 
acampeau Thanks for these steps, I'll try to reproduce them when I have some time.
About
What happens when you don't check that box, or specify "master" here? Would that be a viable workaround for this problem, and if not, why not?