-
Bug
-
Resolution: Cannot Reproduce
-
Major
Hi,
I have a very simple vSphere-based job, where I just shutdown and power-on a VM (on a daily basis). Since installing 2.13, the job started to fail somewhere after the shutdown step with error "ERROR: no workspace for 'name-of-job'". I've downgraded to 2.12 and it works fine again.
This is what I see in console with 2.13:
Started by user username
Building remotely on CPRAN01 (CPRAN01_lbl) in workspace c:\Jenkins\workspace\Restart CPRAN01
[vSphere]
[vSphere] Performing vSphere build step: "Power-Off VM"
[vSphere] Attempting to use server configuration: "DCvSphere - wlcavc03"
[vSphere] Shutting Down VM CPRAN01...
[vSphere] Successfully shutdown "CPRAN01"
ERROR: no workspace for Restart CPRAN01 #132
Finished: FAILURE
And this is what I see with 2.12:
Started by user username
Building remotely on CPRAN01 (CPRAN01_lbl) in workspace c:\Jenkins\workspace\Restart CPRAN01
[vSphere]
[vSphere] Performing vSphere build step: "Power-Off VM"
[vSphere] Attempting to use server configuration: "DCvSphere - wlcavc03"
[vSphere] Shutting Down VM CPRAN01...
[vSphere] Successfully shutdown "CPRAN01"
[vSphere]
[vSphere] Performing vSphere build step: "Power-On/Resume VM"
[vSphere] Attempting to use server configuration: "DCvSphere - wlcavc03"
[vSphere] Waiting for VM CPRAN01 to start (VM may be restarted during this time)
[vSphere] Timeout set to 600 seconds
[vSphere] VM started in 5 seconds
[vSphere] Successfully retrieved IP for "CPRAN01" : 10.8.33.40
[vSphere] Complete startup took 60 seconds
[vSphere] Exposing 10.8.33.40 as environment variable VSPHERE_IP
Finished: SUCCESS
[JENKINS-36085] vSphere 2.13 causes error while restarting VM
Pavel Kudrys
added a comment - Hi,
I'm sorry to report that the problem is still present in recently released 2.14. Am I really alone with this kind of problem?
Pavel Kudrys
added a comment - Hi,
I'm sorry to report that the problem is still present in recently released 2.14. Am I really alone with this kind of problem? 
pjdarton
added a comment - I'm guessing that the answer is "yes, you are alone", as far as this problem goes.
To diagnose this, we'll need lots of logs.
Manage Jenkins -> System Logs, add a new logger, call it "vSphere".
Into that, add the following "Loggers":
vsphere-cloud
org.jenkinsci.plugins.folder
org.jenkinsci.plugins.vSphereCloud
org.jenkinsci.plugins.vSphereCloudLauncher
org.jenkinsci.plugins.vSphereCloudProvisionedSlave
org.jenkinsci.plugins.vSphereCloudRunListener
org.jenkinsci.plugins.vSphereCloudSlave
org.jenkinsci.plugins.vSphereCloudSlaveComputer
org.jenkinsci.plugins.vSphereCloudSlaveTemplate
org.jenkinsci.plugins.workflow
org.jenkinsci.plugins.vsphere
each at loglevel "ALL"
Then try your tests again and see what gets logged.
(also, please tell me what version of the plugin you're using - line numbers tend to change from version to version)
pjdarton
added a comment - I'm guessing that the answer is "yes, you are alone", as far as this problem goes.
To diagnose this, we'll need lots of logs.
Manage Jenkins -> System Logs, add a new logger, call it "vSphere".
Into that, add the following "Loggers":
vsphere-cloud
org.jenkinsci.plugins.folder
org.jenkinsci.plugins.vSphereCloud
org.jenkinsci.plugins.vSphereCloudLauncher
org.jenkinsci.plugins.vSphereCloudProvisionedSlave
org.jenkinsci.plugins.vSphereCloudRunListener
org.jenkinsci.plugins.vSphereCloudSlave
org.jenkinsci.plugins.vSphereCloudSlaveComputer
org.jenkinsci.plugins.vSphereCloudSlaveTemplate
org.jenkinsci.plugins.workflow
org.jenkinsci.plugins.vsphere
each at loglevel "ALL"
Then try your tests again and see what gets logged.
(also, please tell me what version of the plugin you're using - line numbers tend to change from version to version) 
Am I alone who is experiencing this issue? I've just updated Jenkins with latest 2.25 and all plugins. vSphere plugin v. 2.13 still fails to restart VMs with this error: "ERROR: no workspace for 'name-of-job'". V 2.12 works as expected.