|
||||||||
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 |
- [JIRA] (JENKINS-13837) vSphere Plugin not power... jswa...@alohaoi.com (JIRA)
- [JIRA] (JENKINS-13837) vSphere Plugin not ... jswa...@alohaoi.com (JIRA)
- [JIRA] (JENKINS-13837) vSphere Plugin not ... jswa...@alohaoi.com (JIRA)
- [JIRA] (JENKINS-13837) vSphere Plugin not ... jswa...@alohaoi.com (JIRA)
- [JIRA] (JENKINS-13837) vSphere Plugin not ... srinat...@gmail.com (JIRA)
- [JIRA] (JENKINS-13837) vSphere Plugin not ... srinat...@gmail.com (JIRA)
- [JIRA] (JENKINS-13837) vSphere Plugin not ... srinat...@gmail.com (JIRA)
- [JIRA] (JENKINS-13837) vSphere Plugin not ... srinat...@gmail.com (JIRA)
That takes care of the easy troubleshooting - now for the hard stuff.
Are you trying to start the slave via the slave page (Launch Slave Agent), or are you trying to start the slave by having a job that requires the slave?
Is the slave setup to talk to a VM and optional snapshot properly? In other words, does the "Test VM Connection" pass? Also, if using a snapshot, do you have any other slaves using the same VM with different snapshots?
Do you have "Force VM Launch" enabled? And is "Delay between launch and boot complete" set to a reasonable value?
How is the slave agent set to connect - what is the value(s) fo the "Secondary Launch Method"? What about the "Availability" settings?
Do you see any actions from Jenkins in the vCenter logs?