I've debugging an issue where a workflow inserted at the WFStubMachineProvisioned fails because no vCACvm is returned (looking up through the virtualMachineId).
At first I thought there was a logic bug in the workflow, but as it turns out the VM is actually missing from the vCAC inventory, at least as seen from vCO.
So, thinking out loud: When a VM blueprint is being provisioned, and reaches the MachineProvisioned stage, it aparently does not (yet?) exist in the vCAC inventory, causing any workflows which attempt to look up metadata through the vCAC inventory will fail.
This sounds like a pretty nasty catch-22 but presumably is not expected behaviour.
I've had to disable the Inventory service in vCO - could it be that this is causing a mismatch between the internal state in vCAC and the cached state as seen by vCO? Or is this some weird limbo state where the VM is actually missing from vCAC?
