|
||||||||
|
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.
Not certain how long this will take to resolve. I haven't been able to reproduce the problem on the test systems that I have, so I can't be certain if any code changes will fix your situation - or make it worse.
There are a couple things that might help figure out what's going on though:
1) Is Wait for VMTools checked? And do you have VMTools installed on the VM?
2) What value are you using for "Delay between launch and boot complete"?
3) What "Secondary launch method" are you using.
I know that it is possible to get the behavior you describe by NOT checking Wait for VMTool and having a "Delay between launch and boot complete" of 0.