I use the action that waits for the hostname to be set to whatever is expected to, and it runs fine. Whenever I've had issues, it's been because the inputs into the action are not set correctly or have been inadvertently reset due to a scripted action where they were accidentally added as outputs due to click happiness (mainly the check and timeout values are set to null after an attribute reset). Have you watched the vCO workflow during execution to see what's occurring and what the state of the vCenter VM is? In particular, you should see if the workflow is actually sitting there and waiting, as opposed to timing out nearly immediately.
↧