For our staging cluster we are overprovisioning host resources with
RESERVED_MEM="-25% on the cluster template. In this case the overcommit values are only applied on the cluster template, the host template
RESERVED_MEM are blank. When adding a host with 128GB RAM and 32 cores to the cluster I would expect the reported memory capacity to be 160GB (128 * 1.25) and reported CPU capacity to be 4800 (32 * 1.5 * 100).
What actually happens is that the “Overcommitment” section in Sunstone displays the expected values, but the capacity section shows that the memory and CPU overcommitment factors have been applied twice, so memory is reported as 196GB ( 128 * 1.25 * 1.25) and CPU is 7200 (32 * 1.5 * 1.5 * 100) (see attached).