This is a known issue affecting VMware Cloud Director 10.2.x and 10.3.x versions.
The issue is resolved in VMware Cloud Director 10.4 available at
VMware Downloads.If you cannot upgrade to Cloud Director 10.4, please use the workaround specified in the
Workaround section.
Workaround:
- Open an SSH session to each cell.
- Set the workaround: /opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n consoleproxy.cores.max -v "0"
- List the new default: /opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n consoleproxy.cores.max -l
- Restart the cell one at a time to implement the changes: systemctl restart vmware-vcd
Please note if you are only running one cell, this will involve downtime.