|
||||||||
|
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/groups/opt_out.
If I understand this correctly, you're attempting to run a job on Slave "srv1". Slave "srv1" is VM "myserver". And the job is trying to turn on "myserver"? In other words, your job is attempting to power on the slave that it's running on? If that's your intent, that won't work.
Jenkins only allows you to run jobs on slaves that are powered on and connected. You can't power on the slave that you're running the job on because Jenkins won't let you run the job on the slave UNTIL its powered on and connected.
Thankfully, vSphere Cloud Slaves can handle this. If you setup the slave like you have (although I would recommend checking "Wait for VMTools" if you have them installed), then sending a job to that slave will automatically cause the slave to launch, if it's not already powered on. So there's no need for the power-on step in the job.
If you intend to manipulate the slave VM as part of a Job (power on, power off, revert, clone), then you need to do it from a Job running elsewhere besides the slave.