Closed gianlucapiccolo closed 1 year ago
Hi @gianlucapiccolo,
a Compute Resource with no CPU and no Memory (null, not zero) is suspicious. The "LIMITED user" might be a hint to the problem here. Please run...
mysql --binary-as-hex vspheredb -e "SELECT * from object where uuid = UNHEX('c6cc8cc2f8755b73-9d4e169c05a928d7')\G"
...and then check in your vCenter, whether your user is able to see this ComputeResource.
Thanks, Thomas
Confirmed: root cause here is a restricted User, which sees those Cluster Compute Resources, but isn't allowed to read their properties.
Expected Behavior
The task
Compute Resources
should never fail.Current Behavior
In the logs of the daemon I've found this:
Steps to Reproduce
I don't have a way to reproduce it but I have some context:
Your Environment