An administrator has enabled the allocation model in a policy and set the CPU overcommit ratio to 4:1 for all vSphere clusters in a vSphere datacenter.
Why would vRealize Operations report that the cluster has 0 days remaining when the actual CPU overcommit ratio is less than the 4:1 configured value?
vRealize Operations might report that the cluster has 0 days remaining when the actual CPU overcommit ratio is less than the 4:1 configured value because the CPU demand in the cluster is greater than the total CPU capacity. This happens if the cluster's CPU demand consumes all available capacity, leading to an overcommitment situation despite the configured ratio.
For me The CPU demand in the cluster is greater than the total CPU capacity