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

"VM cannot be started" repeatedly with vSphere plugin

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • vsphere-cloud-plugin
    • None
    • Jenkins master on RedHat
      vSphere plugin used w/ ESXI host

      I've been using the vSphere plugin for 6 months or so successfully.

      A couple of weeks ago, it started failing builds with "VM cannot be started" errors. It seems to happen about 50% of the time and could fail twice and then work fine a couple of minutes later.

      Procedure for this particular job is to revert the VM to snapshot, then power off, then power on.

      The ESXI host shows no issues. The event log shows the VM being started fine and it comes up working fine despite Jenkins declaring it failed.

      Timeout is set to 600 sec, but the failures happen after ~1.5 min. A normal run takes about 2.5 min for the IP to become available, so the fail is triggered before the IP would normally be there.

      Is there any debug log I could look into or is this a known issue?

      Log:

      [vSphere]
      [vSphere] Performing vSphere build step: "Power-On/Resume VM"
      [vSphere] Attempting to use server configuration: "sandbox"
      [vSphere] Waiting for IP (VM may be restarted during this time)
      [vSphere] vSphere Error: VM cannot be started
      Build step 'vSphere Build Step' marked build as failure
      Email was triggered for: Failure

            Unassigned Unassigned
            bhavenst Bryan Havenstein
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: