![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Unassigned |
|
Components:
|
vsphere-cloud |
|
Created:
|
03/Mar/14 9:29 PM
|
|
Description:
|
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
|
|
Environment:
|
Jenkins master on RedHat
vSphere plugin used w/ ESXI host
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Bryan Havenstein
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
