[JIRA] (JENKINS-60165) EC2-Fleet-Plugin assigns instance name (‘Jenkins’ doesn’t have label ‘nonprodslave2’; ‘user2’ lacks permission to run on ‘nonprodslave2 i-************343’) after the label. This fails the role assignment by agent labels

[arindom.sar...@gmail.com (JIRA)]

Title: Message Title

Arindom Sarkar commented on JENKINS-60165   Re: EC2-Fleet-Plugin assigns instance name (‘Jenkins’ doesn’t have label ‘nonprodslave2’; ‘user2’ lacks permission to run on ‘nonprodslave2 i-************343’) after the label. This fails the role assignment by agent labels Artem Stasiuk Not sure if I understand how jobs will be scheduled on specific slaves if EC2-Fleet does not assign any label or node name. Say I have a Job which I want to run on a specific slave, we usually put the slave label in "Restrict this job to" field in the job or in the pipeline code. And I could see that is working today where jobs are provisioned on specific slave labels. Just that the node name is not assigned properly. Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203117.1573718238000.2251.1575656880373%40Atlassian.JIRA.