Invalid parameter: Hosts collection cannot be empty. /var/log/vmware/vcf/domainmanager/domainmanager.log, below entries can be found indicating that the host collection is null or empty during the disconnect task:Contract task Disconnect ESXi Host input: {"vcRemoteEndpoint":{"address":"<vcenter FQDN>","port":0,"username":"<user account>","password":"*****"},"hostnames":[],"continueOnFailure":false,"_executeRetrialCount":0,"_preValidationRetrialCount":0,"_maxRetriesCount":3}Tracking ContinueOnFailure false flag, Max Retry Count 3 and pre Validate Retry Count 0VCF_ERRORS_GENERIC_INPUT_PARAM_ERROR Invalid parameter: Hosts collection cannot be empty com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Invalid parameter: Hosts collection cannot be emptySDDC manager 5.2.x
This issue typically occurs when the cluster is already empty. SDDC Manager's standard workflow is designed to prevent clusters from reaching an "empty" state. If hosts were manually removed from the inventory (e.g., via direct database manipulation or external vCenter actions) instead of using the SDDC Manager workflow, the standard "Delete Cluster" workflow fails.
To remove an orphaned or empty cluster that cannot be deleted via the standard GUI workflow, use the Force Delete option via the SDDC Manager API.
Steps:
DELETE /v1/clusters/{id}?force=true