VMware Cloud Community
schistad
Enthusiast
Enthusiast

Bug in vCO helper "Prepare Workflow Run"?

A few days ago I attached a new vCO workflow to the provisioned stub as part of testing Host Affinity groups. This broke the provisioning process, causing new VMs to be deleted.

On inspection I discovered that the vCO parameter 'vCACvm' was not being set, causing the entire chain of workflows to break.

This parameter is requested by 'WFStubMachineProvisioned', as output parameter from 'Prepare Workflow Run'. I can see that the parameter is not being returned.

Digging further, I noticed that 'Prepare Workflow Run' contains the step 'Get vCAC VM' which actually tries to use the parameter 'vCACVM' as _both_ input AND output. This is something I've discovered is impossible - you cannot set the same parameter both as IN and OUT for a workflow Item.

If memory serves, any parameter used as IN will be unreturnable, and this would explain why the workflow is not setting vCACVM properly. But I can't edit the workflow to test.

Anyone else here seen this problem?

Reply
0 Kudos
1 Reply
schistad
Enthusiast
Enthusiast

Further digging has revealed that the problem actually lies in the inventory of either vCAC or vCO - probably the latter.

Specifically, I've realized that new VMs are not showing up in the vCAC Virtual Machines inventory of vCO. So somewhere there must be a cached state which is not refreshing, and it could be on either side - I do not know wether vCO actually caches this or just requests a list from vCAC when browsed.

But this obviously causes issues when attempting to retrieve metadata from a fresh VM during deployment - if it does not exist in the inventory everything breaks.

I've created a thread over at the vCO forums, but I do not yet know which side is having the issue.

Question: Can I browse the inventory of vCAC without vCO?

Reply
0 Kudos