|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
I still intend to try to provide detailed instructions for reproducing the problem, but the fact that people are able to work around it by removing this property seems to suggest that my original theory may be correct: once the node is used one time to run a job that uses the Xvnc plugin, this property appears, and after the property is there, configuration of the node fails in this way. I'll see if that formula works on a clean install. Removing properties and reloading is not a practical workaround for my installation. We scale up and down from between a small handful to several hundred nodes and are constantly churning through nodes. Reloading configuration from disk is not practical for us. In any case, since we churn through nodes, I'm not heavily handicapped by this.