VCD virtual appliance experiences intermittent outages with incorrect vCPU allocation

Products

• VMware Cloud Director

Issue/Introduction

The VCD virtual appliance is configured with an insufficient number of vCPUs (e.g., fewer than 8).

The following error is observed in the /opt/vmware/vcloud-director/logs/vmware-vcd-watchdog.log:

<YYYY-MM-DD> <Time> | WARN  | wget failed, return code: 4, will retry in 30 seconds

The following information is observed in the /opt/vmware/vcloud-director/logs/cloud-health-<Time>.log file:

CPU         : 4 @ 2.30GHz
CPU Size :: Small or Legacy Application

Collecting VCD support bundles may cause the VCD service to crash; "systemctl status vmware-vcd" will show the status as "active (exited)".

Environment

VMware Cloud Director 10.6.x

Cause

The smallest recommended configuration for production deployments is a three-node deployment of Medium-sized virtual appliances, which requires at least 8 vCPUs; however, an inadequate number of vCPUs (e.g., 4) is currently being used for the virtual appliance.

Resolution

Follow the VMware Cloud Director Appliance Sizing Guidelines and allocate additional vCPUs to the virtual appliance as required.

If the vmware-vcd service status is "active (exited)", use the following command to recover the service:

systemctl restart vmware-vcd