Any attempt to modify VM NICs or general VM/vApp settings fails with the following error:
“The operation could not be performed because the argument is invalid. A specified parameter was not correct: val[0]”
The /opt/vmware/vcloud-director/logs/vcloud-container-debug.log shows the following entries at the time of failure:
From the logs, it appears that during the vApp update/editing process,a specific memory value (104,857,600 bytes) is being requested.
Although the resource pool reflects a memory reservation of 0 MB, vCenter reports unreserved = 0, resulting in an InsufficientMemoryResourcesFault for the backing resource pool.
The failure originates from the vCenter side and is surfaced in vCD as the generic “val[0]” error.
VMware Cloud Director 10.x
This is due to stale memory reservation data residing in the resource_pool_inv table that does not reflect the actual state in vCenter. It appears the VCD database maintains "phantom" reservations, causing vCenter to reject reconfiguration tasks with an InsufficientMemoryResourcesFault (Error: val[0]).
To resolve this issue , the stale memory reservation data from the resource_pool_inv table needs to be cleared
Before proceeding, please ensure the following precautions are taken:
Take a full VMware Cloud Director Database Backup
Take snapshots of all vCD cells to allow rollback in case of any unexpected impact.
Once these necessary safeguards have been completed, you will need to contact Broadcom Support, as the steps to clear the stale memory reservation data requires direct modification of the database.