|
||||||||
|
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.
Sorry, there's no additional logging in this portion of the code.
At the point where you are seeing the failure, the plugin is has sent a "Power On" command to the vCenter. That command queues up in vCenter and is processed. When the command is complete, it only means that the VM has been powered on, not that it is fully powered up and ready to go. You should be able to observe this behavior in vCenter if you power on a VM via one of the vSphere Clients (web or app). The Task name is "Power On virtual machine". Depending on how vCenter is configured, this command can execute very quickly, or more slowly, for example - if your vCenter is using DRS and the VM has to be migrated to another host before powering on.
Anyway, the plugin has a 15 second delay, waiting for that task to complete. If the task doesn't complete in that amount of time, you get the error message that you did. In testing and in production, 15 seconds seems to have been adequate. But maybe it needs to be higher...
If you could replicate the problem, then find the associated "Power On virtual machine" task in the vCenter task viewer, then find out the elapsed time between its Start Time and Completed Time. If the time is greater than 15 seconds, we know what the problem is - and how to solve it. If the time is much less than 15 seconds - we'll have to troubleshoot some more.