[JIRA] (JENKINS-59431) When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node

17 views
Skip to first unread message

yotu.tuy@gmail.com (JIRA)

unread,
Sep 18, 2019, 9:37:02 AM9/18/19
to jenkinsc...@googlegroups.com
Karolina Arancibia Valuskova created an issue
 
Jenkins / Bug JENKINS-59431
When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Issue Type: Bug Bug
Assignee: Dominik Bartholdi
Components: nodelabelparameter-plugin
Created: 2019-09-18 13:36
Environment: Jenkins ver 2.176.3
Node and Label parameter plugin ver. 1.7.2
Parametrized Trigger plugin ver 2.35.2
Labels: nodelabelparameter
Priority: Major Major
Reporter: Karolina Arancibia Valuskova

I've 6 similar nodes, that share a label "TESTPC" when I configure the job to trigger with that label the plugin works fine as it triggers on all 6 nodes.

I have added the label "TESTPC1", "TESTPC2", and so on in each node since every now and then we want to run the job on only one specific node, however what ends up happening is that the job is run in any of the computers that have the "TESTPC" label and only in one (most usually not the intended one). I also tried putting a label that doesn't share the any letter with the other labels on my node ("banana") but the problem still persists.
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

yotu.tuy@gmail.com (JIRA)

unread,
Jan 10, 2020, 7:35:02 AM1/10/20
to jenkinsc...@googlegroups.com
Karolina Arancibia Valuskova commented on Bug JENKINS-59431
 
Re: When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node

There is a similar problem when there are two groups of nodes : 6 nodes with TESTPC label and 6 nodes with PRODPC label. The plugin would send the run call to all of them regardless of the label they have, this is a big issue of broken functionality.

yotu.tuy@gmail.com (JIRA)

unread,
Jan 10, 2020, 8:59:02 AM1/10/20
to jenkinsc...@googlegroups.com
Karolina Arancibia Valuskova updated an issue
 
I've 6 similar nodes, that share a label "TESTPC" when I configure the job to trigger with that label the plugin works fine as it triggers on all 6 nodes.

 {{ I have added the label "TESTPC1", "TESTPC2", and so on in each node since every now and then we want to run the job on only one specific node, however what ends up happening is that the job is run in any of the computers that have the "TESTPC" label and only in one (most usually not the intended one). I also tried putting a label that doesn't share the any letter with the other labels on my node ("banana") but the problem still persists.
}}

{{-The same applies when I have groups of different nodes with a single label. }}
{{-There is the same problem with the Node - Factory part of the plugin.}}

{{Here is the log of a build that should have run on TESTPC1,2 and 3, but instead run on TESPC 5 (twice) and PRODPC6 (PC with different label)}}
{code:java}
Started by user [8mha:////4GcLNmTz8oi6tKjMMjxnTRRbUCKLrip2lyOZlKIRHdypAAAAmx+LCAAAAAAAAP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAyuEgZ+/dLi1CL94syUktTiktQiAKFXgYvEAAAA [0m<USER>
Running as SYSTEM
Building remotely on [8mha:////4JNmtgR2g18637CcH5OrJjPvakAXl1al6Pij6HjPxIbMAAAAnR+LCAAAAAAAAP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAz2EgZB/eT83ILSktQi/WBnR78AZzMAOdpwt8YAAAA= [0mTESTPC6 (TESTPC) in workspace C:/jenkins/workspace/<TRIGGER JOB NAME>
define: [LabelParameterValue: NODELABEL=TESTPC1]
define: [LabelParameterValue: NODELABEL=TESTPC2]
define: [LabelParameterValue: NODELABEL=TESTPC3]
Triggering projects: [8mha:////4GEYBZuNUHdwWOzB3SOyspk29pTLutRnS9YcoIxnTpKWAAAAlx+LCAAAAAAAAP9b85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyTVzHb1RttJBUeZGJg8GdhyUvPSSzJ8GJhLi3JKGIR8shLLEvVzEvPS9YNLijLz0q0rihik0IxzhtAgwxgggJGJgaGiAMgQKGEQ08/KT9J3zSvLLMrPy03NKwlOLSkt0AcArVNUhJsAAAA= [0m<JOB NAME>
Finished: SUCCESS{code}
Which seems to indicate that the job was send to build before the nodes were selected.

 

yotu.tuy@gmail.com (JIRA)

unread,
Jan 10, 2020, 9:00:03 AM1/10/20
to jenkinsc...@googlegroups.com

yotu.tuy@gmail.com (JIRA)

unread,
Jan 10, 2020, 9:00:03 AM1/10/20
to jenkinsc...@googlegroups.com
Karolina Arancibia Valuskova updated an issue
I've 6 similar nodes, that share a label "TESTPC" when I configure the job to trigger with that label the plugin works fine as it triggers on all 6 nodes.

{{I have added the label "TESTPC1", "TESTPC2", and so on in each node since every now and then we want to run the job on only one specific node, however what ends up happening is that the job is run in any of the computers that have the "TESTPC" label and only in one (most usually not the intended one). I also tried putting a label that doesn't share the any letter with the other labels on my node ("banana") but the problem still persists.}}

{{-The same applies when I have groups of different nodes with a single label.   i.e. 12 nodes 6 with TESTPC and 6 with PRODPC }}

{{-There is the same problem with the Node - Factory part of the plugin.}}

{{Here is the log of a build that should have run on TESTPC1,2 and 3, but instead run on TESPC 5 (twice) and PRODPC6 (PC with different label)}}
{code:java}
Started by user [8mha:////4GcLNmTz8oi6tKjMMjxnTRRbUCKLrip2lyOZlKIRHdypAAAAmx+LCAAAAAAAAP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAyuEgZ+/dLi1CL94syUktTiktQiAKFXgYvEAAAA [0m<USER>
Running as SYSTEM
Building remotely on [8mha:////4JNmtgR2g18637CcH5OrJjPvakAXl1al6Pij6HjPxIbMAAAAnR+LCAAAAAAAAP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAz2EgZB/eT83ILSktQi/WBnR78AZzMAOdpwt8YAAAA= [0mTESTPC6 (TESTPC) in workspace C:/jenkins/workspace/<TRIGGER JOB NAME>
define: [LabelParameterValue: NODELABEL=TESTPC1]
define: [LabelParameterValue: NODELABEL=TESTPC2]
define: [LabelParameterValue: NODELABEL=TESTPC3]
Triggering projects: [8mha:////4GEYBZuNUHdwWOzB3SOyspk29pTLutRnS9YcoIxnTpKWAAAAlx+LCAAAAAAAAP9b85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyTVzHb1RttJBUeZGJg8GdhyUvPSSzJ8GJhLi3JKGIR8shLLEvVzEvPS9YNLijLz0q0rihik0IxzhtAgwxgggJGJgaGiAMgQKGEQ08/KT9J3zSvLLMrPy03NKwlOLSkt0AcArVNUhJsAAAA= [0m<JOB NAME>
Finished: SUCCESS{code}
Which seems to indicate that the job was send to build before the nodes were selected.

 

yotu.tuy@gmail.com (JIRA)

unread,
Jan 10, 2020, 9:01:03 AM1/10/20
to jenkinsc...@googlegroups.com
Karolina Arancibia Valuskova updated an issue
Comment:
There is a similar problem when there are two groups of nodes : 6 nodes with TESTPC label and 6 nodes with PRODPC label. The plugin would send the run call to all of them regardless of the label they have, this is a big issue of broken functionality.

yotu.tuy@gmail.com (JIRA)

unread,
Jan 10, 2020, 9:33:03 AM1/10/20
to jenkinsc...@googlegroups.com
Karolina Arancibia Valuskova updated an issue
Component/s: parameterized-trigger-plugin
Priority: Major Critical

yotu.tuy@gmail.com (JIRA)

unread,
Jan 10, 2020, 9:33:03 AM1/10/20
to jenkinsc...@googlegroups.com
Karolina Arancibia Valuskova updated an issue
Priority: Critical Blocker
Reply all
Reply to author
Forward
0 new messages