[JIRA] (JENKINS-13837) vSphere Plugin not powering up virtual machines

[srinat...@gmail.com (JIRA)]

Srinath C commented on JENKINS-13837 vSphere Plugin not powering up virtual machines I got the issue resolved. VMs are successfully getting launched on the vSphere server now. It was not even related to jenkins or the vSphere Cloud plugin. It was the Leap Second bug on the jenkins server that was causing the problem. I took a jstack of the jenkins process while the slave was stuck at launching and found that the thread was hung at : "pool-6-thread-8" daemon prio=10 tid=0x00007f75d8252800 nid=0x7292 sleeping[0x00007f768651c000] java.lang.Thread.State: TIMED_WAITING (sleeping) at java.lang.Thread.sleep(Native Method) at com.vmware.vim25.mo.Task.waitForTask(Task.java:229) at com.vmware.vim25.mo.Task.waitForTask(Task.java:152) at org.jenkinsci.plugins.vSphereCloudLauncher.launch(vSphereCloudLauncher.java:169) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) After spending a lot of time peeking into the source code I realized that even a simple program to sleep for 1 second using Thread.currentThread().sleep(1000) was also getting stuck indefinitely. Fortunately, I found the reason at http://stackoverflow.com/questions/11294573/thread-sleep-never-returns and a simple reboot of the server solved the problem.

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