[JIRA] [vsphere-cloud-plugin] (JENKINS-28536) Deploy VM from Template no longer working

[markjmanning@markjmanning.com (JIRA)]

Mark Manning created an issue

Jenkins / JENKINS-28536 Deploy VM from Template no longer working Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud-plugin Created: 21/May/15 5:43 PM Environment: Jenkins 1.613 vSphere-cloud-plugin 2.5 VMWare vSphere 5.5 Priority: Minor Reporter: Mark Manning Deploy VM from Template no longer working for me. My configured jobs were working using "Deploy VM from template" with vsphere-cloud-plugin 1.1.12, but stopped working when I upgraded to 2.4. Doesn't work with 2.5 either. Output: >> [vSphere] Performing vSphere build step: "Deploy VM from template" >> [vSphere] Attempting to use server configuration: "vcenterbuild" >> [vSphere] Deploying new vm "TEST123" from template "BaseTemplate" >> [vSphere] Started cloning of VM. Please wait ... >> [vSphere] Exception: org.jenkinsci.plugins.vsphere.tools.VSphereException: vSphere Error: Couldn't clone "BaseTemplate"! Does "TEST123" already exist? Clone task ended with status error The VM TEST123 does not exist and never did exist in my vSphere environment. Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[mengata@gmail.com (JIRA)]

mohamed amin mengat commented on JENKINS-28536

Re: Deploy VM from Template no longer working I have the same problem...the "clone vm from vm or template" build step doesnt work, it throws the same error message. Tested with 2.9 plugin version & vmware esxi 5.0 server.

Add Comment

[mtaylor@opto22.com (JIRA)]

Matt Taylor commented on JENKINS-28536

Re: Deploy VM from Template no longer working

I can't figure this out has anyone else figured it out? Provisioned slave GRW10-64 failed to launch org.jenkinsci.plugins.vsphere.tools.VSphereException: org.jenkinsci.plugins.vsphere.tools.VSphereException: vSphere Error: Couldn't clone "GRW10-64-B"! Does "GRW10-64_5d7c0e81-2573-4c14-8101-b9ad3fe8fe40" already exist? Clone task ended with status error at org.jenkinsci.plugins.vsphere.tools.VSphere.cloneOrDeployVm(VSphere.java:169) at org.jenkinsci.plugins.vsphere.tools.VSphere.cloneVm(VSphere.java:129) at org.jenkinsci.plugins.vSphereCloudSlaveTemplate.provision(vSphereCloudSlaveTemplate.java:250) at org.jenkinsci.plugins.vSphereCloud$1.call(vSphereCloud.java:274) at org.jenkinsci.plugins.vSphereCloud$1.call(vSphereCloud.java:272) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.jenkinsci.plugins.vsphere.tools.VSphereException: vSphere Error: Couldn't clone "GRW10-64-B"! Does "GRW10-64_5d7c0e81-2573-4c14-8101-b9ad3fe8fe40" already exist? Clone task ended with status error at org.jenkinsci.plugins.vsphere.tools.VSphere.cloneOrDeployVm(VSphere.java:164) ... 10 more

Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[pjdarton@gmail.com (JIRA)]

pjdarton commented on JENKINS-28536

Re: Deploy VM from Template no longer working

In plugin version 2.13 (and probably earlier), any problems encountered when creating the VM would result in this "does it already exist" error. I've added extra logging (that should end up in 2.14) and any issues encountered should be viable if you configure Jenkins to log org.jenkinsci.plugins.vsphere, org.jenkinsci.plugins.vSphereCloudProvisionedSlave, org.jenkinsci.plugins.vSphereCloudSlaveTemplate and vsphere-cloud at Log level "ALL".

Add Comment

[pjdarton@gmail.com (JIRA)]

pjdarton closed an issue as Cannot Reproduce

Closing: No response to previous question. Feel free to re-open if there's new evidence.

Jenkins / JENKINS-28536

Deploy VM from Template no longer working

Change By: pjdarton Status: Open Closed Resolution: Cannot Reproduce

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)