Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-36085

vSphere 2.13 causes error while restarting VM

XMLWordPrintable

      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

            Unassigned Unassigned
            odklizec Pavel Kudrys
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: