Hi,
We have recently upgraded from vCO 5.1 to 5.5 and since the upgrade we are experiencing a problem with vim3WaitDnsNameInTools and vim3WaitToolsStarted actions.
Since the upgrade, when using either of these actions in a VM clone workflow, they fail to register a change in the VMTools status on the guest and eventually reach the defined timeout. If the same action is executed again in the same workflow immediately after the time out is reached, it is successful (Assuming because VMTools is already started).
Interestingly, if I use the vim3WaitDnsNameInTools or vim3WaitToolsStarted actions in a workflow which isnt part of a clone operation (ie. I power off a VM, start the workflow and then power on the VM) the actions work correctly.
This same issue occurs in a fresh install of vCO 5.5, and can be replicated in sample workflow that is installed with vCO. (Clone, Windows Sysprep with single NIC and credential)
Has anyone else come across this issue and if so, how were you able to correct it? Any suggestions on other places to look to try determine the exact cause would be helpful. I've tried increasing the level of logging in vCO but the only event that is logged in relation to this is when the action times out.
Thanks