doesn’t have label

74 views
Skip to first unread message

Alok Dubey

unread,
Oct 11, 2023, 12:39:22 PM10/11/23
to Jenkins Users
We recently got into an issue where Jenkins master is failed to schedule/distribute builds even though a lot of build agents are sitting idle. We noticed this problem with both ec2 fleet and ec2 (on-demands) plugins. 

Most of the jobs are stuck in the queue with the following message but nodes with the required labels are up in the UI. 

Anyone has experienced similar behavior? Any suggestions to fix this? Thanks. 
Still waiting to schedule task Waiting for pending items to get a node assigned ‘aws-dev-deploy-6’ doesn’t have label ‘docker’ ‘aws-dev-deploy-8’ doesn’t have label ‘docker’ ‘aws-prod-deploy-5’ doesn’t have label ‘docker’ ‘aws-prod-deploy-6’ doesn’t have label ‘docker’ ‘aws-prod-deploy-7’ doesn’t have label ‘docker’ ‘i-09a2be6382fc26e24’ doesn’t have label ‘docker’ ‘i-0a0347c44f3325130’ doesn’t have label ‘docker’ ‘i-0a2dd9e65b696c5a2’ doesn’t have label ‘docker’ ‘j1-android i-03006f1500a1a0c49’ doesn’t have label ‘docker’ ‘j1-docker i-009e0ccbd3a9616d3’ doesn’t have label ‘docker’ ‘j1-jenkinsfilerunner i-00327f98f2b84ccd0’ doesn’t have label ‘docker’ ‘j1-jenkinsfilerunner i-007332676d8b4a5f6’ doesn’t have label ‘docker’ ‘j1-jenkinsfilerunner i-07a579dbf80a63d27’ doesn’t have label ‘docker’ ‘j1-jenkinsfilerunner i-07c99149550e0be53’ doesn’t have label ‘docker’ ‘j1-jenkinsfilerunner i-08c0f86b1dfeb58c0’ doesn’t have label ‘docker’ ‘j1-jenkinsfilerunner i-0a55498b644f1a18a’ doesn’t have label ‘docker’ ‘j1-jenkinsfilerunner i-0b4f913462a670fa3’ doesn’t have label ‘docker’ ‘j1-jenkinsfilerunner i-0ca4a73a0bb975df6’ doesn’t have label ‘docker’ ‘j1-jenkinsfilerunner i-0dd7e76088df5c56d’ doesn’t have label ‘docker’ ‘j1-jenkinsfilerunner i-0ee7610539156599c’ doesn’t have label ‘docker’ ‘j1-linux i-0058f862d193df3ea’ doesn’t have label ‘docker’ ‘j1-linux i-00656f1ae9f80073a’ doesn’t have label ‘docker’ ‘j1-linux i-012491b4a3876bef0’ doesn’t have label ‘docker’ ‘j1-linux i-0177b40a2676cc70a’ doesn’t have label ‘docker’ ‘j1-linux i-0285a836ca10ea06a’ doesn’t have label ‘docker’ ‘j1-linux i-03bf1b363f722977e’ doesn’t have label ‘docker’ ‘j1-linux i-03dcba2eed6a02624’ doesn’t have label ‘docker’ ‘j1-linux i-03eafa4b54936f82e’ doesn’t have label ‘docker’ ‘j1-linux i-04077c54f1352eaec’ doesn’t have label ‘docker’ ‘j1-linux i-059e9e4d333245344’ doesn’t have label ‘docker’ ‘j1-linux i-08559e6d9be2dab5c’ doesn’t have label ‘docker’ ‘j1-linux i-08dfca6d3b1176a11’ doesn’t have label ‘docker’ ‘j1-linux i-090bee3bdf40db6ea’ doesn’t have label ‘docker’ ‘j1-linux i-09a71e57be1518373’ doesn’t have label ‘docker’ ‘j1-linux i-0a06b985fea4aeef7’ doesn’t have label ‘docker’ ‘j1-linux i-0b868611590a750a6’ doesn’t have label ‘docker’ ‘j1-linux i-0e5597e6c71593762’ doesn’t have label ‘docker’ ‘j1-linux i-0f8bd2f10aaf9aa11’ doesn’t have label ‘docker’ ‘j1-linux i-0fd49a3eeb2c6d1a1’ doesn’t have label ‘docker’

Mark Waite

unread,
Oct 11, 2023, 2:07:29 PM10/11/23
to Jenkins Users
I've sometimes seen something like that when working with the static agents that I have connected to my controller.  I workaround the problem by adding a "junk" label to any one of the agents.  After saving the junk label, I configure the agent again to remove the "junk" label and that seems to cause jobs to again recognize agent labels.

Björn Pedersen

unread,
Oct 12, 2023, 9:55:50 AM10/12/23
to Jenkins Users
Affected by https://issues.jenkins.io/browse/JENKINS-71937?  Should be fixed in latest weekly (2.427).

Mark Waite

unread,
Oct 12, 2023, 9:58:46 AM10/12/23
to Jenkins Users
On Thursday, October 12, 2023 at 7:55:50 AM UTC-6 you wrote:
Mark Waite schrieb am Mittwoch, 11. Oktober 2023 um 20:07:29 UTC+2:
I've sometimes seen something like that when working with the static agents that I have connected to my controller.  I workaround the problem by adding a "junk" label to any one of the agents.  After saving the junk label, I configure the agent again to remove the "junk" label and that seems to cause jobs to again recognize agent labels.

 
Affected by https://issues.jenkins.io/browse/JENKINS-71937?  Should be fixed in latest weekly (2.427).

Possibly, though I've used my workaround for many months and that issue was only introduced in in Jenkins 2.426.
 
Reply all
Reply to author
Forward
0 new messages