Issue Deploying Multi-VM vAPP in vcloud from vCAC

[VirExprt]

Hello,

Has anyone encountered issue with vCloud Director while provisioning Multi-VM vAPP using vCAC?

i am facing this issue while Provisioning Multi-VM vApp from vCAC, initially everything looks promising , but while in middle of provisioning error occurs at vCAC

after this error, the vapp is removed from the My Machine listing while vApp is still exists in vCloud director.

checking Log Viewer found below error entry

the Stack Trace is as below

"at DynamicOps.VCloudModel.Interface.VCloudManagementServices.WaitForTask(Task task, Int32 periodInSeconds, Int32 retryCount) at DynamicOps.VCloudModel.Interface.VCloudManagementServices.CreateVAppFromTemplate(String vdcId, String appName, String templateName, String networkName, String storageName, String templateHref) at DynamicOps.VCloudModel.Activities.VCloudCreateVAppFromTemplate.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)"

it looks like to me this could be the issue of wait time for Workflow to Expire or terminate the Process.

Reson for this assumption is, If i Provision vApp with Single VM , it provision very smoothly and get PowerON as well.

Any thoughts!!!

Regards,

MG

[AdamBohle]

Does this vApp template clone out fine in vCloud Director if you take vCAC out of the equation?

[VirExprt]

Hello Adam,

It very much clone it directly from  vCloud infact when the blueprint initiate clone process it wait for around 10 mins to finish clone in vcloud but it suddenly display error and terminate the process in vCAC whereas the same clone process keeps on going until cloning is completed.

Br,

MG

[VirExprt · Accepted solution]

This had been taken as Bug by VMware Support which is fixed in New Release 5.2

55734

[Provisioning/vCD] A programmed time out of 10 minutes occurs when provisioning a vApp

that requires an extended amount of time to fini

sh cloning. To resolve th

is issue, a new vCloud

activity timeout global property, Activity Task

Timeout, was added and affects the timeout for all

vCloud activities, such as inventory data co

llection, power options, and provisioning. The

default is 30 minutes and can be changed

by the vCAC administrator as required.