[JIRA] [vsphere-cloud] (JENKINS-22025) "VM cannot be started" repeatedly with vSphere plugin

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

Jerry Maloney commented on JENKINS-22025 "VM cannot be started" repeatedly with vSphere plugin I'm seeing similar behavior. I'm just getting started with this plugin and I'm running very simple tests right now on two VMs. For both VMs, the Jenkins job A. creates a file at /tmp/AppIsInstalled B. reverts the VM C. powers on the VM D. verifies that /tmp/AppIsInstalled (thus verifying that the app is no longer installed in my toy scenario) This succeeds on one VM and fails on another. The failure is: SSH: Connecting from host [jenkins] SSH: Connecting with configuration [NPD-ars-app-01.builder] ... SSH: EXEC: STDOUT/STDERR from command [# the next line installs ARS echo "this file means ARS is installed and working" > /tmp/ArsIsInstalled ] ... SSH: EXEC: completed after 202 ms SSH: Disconnecting configuration [NPD-ars-app-01.builder] ... SSH: Transferred 0 file(s) [vSphere] [vSphere] Performing vSphere build step: "Revert to Snapshot" [vSphere] Attempting to use server configuration: "NPD vSphere" [vSphere] Reverting to snapshot "base" for VM phlq1cfldars001... [vSphere] Complete. [vSphere] [vSphere] Performing vSphere build step: "Power-On/Resume VM" [vSphere] Attempting to use server configuration: "NPD vSphere" [vSphere] Waiting for IP (VM may be restarted during this time) [vSphere] Error: Could not get IP for "phlq1cfldars001" Build step 'vSphere Build Step' marked build as failure Notifying upstream projects of job completion Finished: FAILURE The succeeding output is: SSH: Connecting from host [jenkins] SSH: Connecting with configuration [NPD-cds-grid01.builder] ... SSH: EXEC: STDOUT/STDERR from command [# the next line installs CDS (this is much easier than you thought it was) echo "this file means CDS is installed and working" > /tmp/CdsIsInstalled] ... SSH: EXEC: completed after 202 ms SSH: Disconnecting configuration [NPD-cds-grid01.builder] ... SSH: Transferred 0 file(s) [vSphere] [vSphere] Performing vSphere build step: "Revert to Snapshot" [vSphere] Attempting to use server configuration: "NPD vSphere" [vSphere] Reverting to snapshot "base" for VM phlpdccdsgrd001... [vSphere] Complete. [vSphere] [vSphere] Performing vSphere build step: "Power-On/Resume VM" [vSphere] Attempting to use server configuration: "NPD vSphere" [vSphere] Waiting for IP (VM may be restarted during this time) [vSphere] Successfully retrieved IP for "phlpdccdsgrd001" : 10.114.72.20 SSH: Connecting from host [jenkins] SSH: Connecting with configuration [NPD-cds-grid01.builder] ... SSH: EXEC: STDOUT/STDERR from command [# after revert, check to make sure CDS is not installed ls /tmp/CdsIsInstalled # we expect this to be missing if [ $? -eq 2 ]; then exit 0 else exit 1 fi ] ... ls: cannot access /tmp/CdsIsInstalled: No such file or directory SSH: EXEC: completed after 407 ms SSH: Disconnecting configuration [NPD-cds-grid01.builder] ... SSH: Transferred 0 file(s) Notifying upstream projects of job completion Finished: SUCCESS Now on the VM where it fails, everything works correctly, by which I mean the VM is reverted and restarted, and the /tmp file is deleted. I can verify this manually. The only part that fails is where Jenkins fails to return to the program flow. I don't know enough about vSphere to know if this is something about how the failing VM is configured. I'm talking with my data center folks to try to figure this out, but this ticket looks so similar to my behavior that I wonder if it is the same cause.

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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.