Just to clarify that I understand the problem - what you are seeing is that on line# 7 of the shutdownVM action
var status = vm.runtime.powerState.value;
the status variable never changes its value, and the action throws an exception after the provided timeout elapses?
What is the value of timeout parameter when you call this action? Is it possible that the VM guest OS shutdowns very slowly and the provided timeout is not enough? Could you check with larger timeout?
Yes, that is the correct line. The timeout is 5mins and the VMs are shutting down within 90 seconds.
Something I just thought is worth noting, I have a workflow scheduled for every 30 minutes that traverses each VM on each host in each cluster to get a total of the VM memory for each cluster.
Hello, i am experiencing a similar problem when starting vm : the state is not updated correctly on my object vm but is correct in the vsphere client.
Did you find a solution or a workaround for your problem ?
1 person found this helpful
We have had few issues with the vRO cache getting stale and the value not updated when needed.
We are trying to resolve this by deploying the latest vCenter plugin in our environment:
So far it looks good. :-)
HI, we have a same issue. Is there any solution?