|
||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||
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.
For more options, visit https://groups.google.com/d/optout.
Config issue I think. I don't know whether there are legitimate use cases for giving one node's self label (i.e. node name) as regular label to another node, but it's really just asking for trouble, as this issue shows. Don't do that, and you should be fine.
In the meantine reducing priority as the workaround is easy and obvious: Do not assign labels with the same name as a node to other nodes.