Failed to deploy. No suitable host found for the requested NSX Advanced Load Balancer Controller form factor

Products

• VCF Operations

Issue/Introduction

• "Failed to deploy. No suitable host found for the requested NSX Advanced Load Balancer Controller form factor - LARGE" is reported while deploying Load Balancer VM  on VCF Management Domain
• This issue is seen if vSAN/NFS V3/VMFS on Fibre Channel (FC) is not present in Management Domain as a storage solution
• /var/log/vmware/vcf/domainmanager/domainmanager.log

YYYY-MM-DDTHH:MM:SS DEBUG [vcf_dm,<OP ID>,<OP ID>] [c.v.v.n.c.v.v.ALBClusterValidator,http-nio-127.0.0.1-7200-exec-6]  [ALB] Checking <Host ID> Esxi for ALB deployment
YYYY-MM-DDTHH:MM:SS DEBUG [vcf_dm,<OP ID>,<OP ID>] [c.v.v.n.c.v.v.ALBClusterValidator,http-nio-127.0.0.1-7200-exec-6]  [ALB] Insufficient disk space 0 MB in host required 1467392 MB
YYYY-MM-DDTHH:MM:SS DEBUG [vcf_dm,<OP ID>,<OP ID>] [c.v.v.n.c.v.v.ALBClusterValidator,http-nio-127.0.0.1-7200-exec-6]  [ALB] Found suitable hosts: []
YYYY-MM-DDTHH:MM:SS DEBUG [vcf_dm,<OP ID>,<OP ID>] [c.v.v.c.n.s.c.c.ApiConnection,http-nio-127.0.0.1-7200-exec-6]  Closed ApiClient connection.
YYYY-MM-DDTHH:MM:SS ERROR [vcf_dm,<OP ID>,<OP ID>] [c.v.v.n.c.v1.NsxALBClusterController,http-nio-127.0.0.1-7200-exec-6]  NSX ALB validation failed with errors [ECM_ALB_NO_SUITABLE_HOST_FOUND]
YYYY-MM-DDTHH:MM:SS ERROR [vcf_dm,<OP ID>,<OP ID>] [c.v.v.n.c.v1.NsxALBClusterController,http-nio-127.0.0.1-7200-exec-6]  Failed to create NSX Advanced Load Balancer cluster
com.vmware.evo.sddc.common.core.error.CompositeInvalidInputException: Avi Load Balancer spec validation failed
YYYY-MM-DDTHH:MM:SS ERROR [vcf_dm,<OP ID>,<OP ID>] [c.v.e.s.e.h.LocalizableRuntimeExceptionHandler,http-nio-127.0.0.1-7200-exec-6]  [<>] NSX_ALB_VALIDATION_FAILED Avi Load Balancer spec validation failed
com.vmware.evo.sddc.common.core.error.CompositeInvalidInputException: Avi Load Balancer spec validation failed
YYYY-MM-DDTHH:MM:SS DEBUG [vcf_dm,<OP ID>,<OP ID>] [c.v.e.s.e.h.LocalizableRuntimeExceptionHandler,http-nio-127.0.0.1-7200-exec-6]  Handler Error Response: {"errorCode":"NSX_ALB_VALIDATION_FAILED","arguments":[],"message":"Avi Load Balancer spec validation failed","nestedErrors":[{"errorCode":"ECM_ALB_NO_SUITABLE_HOST_FOUND","arguments":["LARGE"],"message":"No suitable host found for the requested Avi Load Balancer Controller form factor - LARGE."}],"referenceToken":"<>"}

Environment

VCF 9.x

Cause

This deployment exception is triggered when datastores not supported for greenfield (other than vSAN, VMFS-FC, NFS3) is designated as the only target storage solution across the cluster.

While datastores other than above are supported for brownfield import and lifecycle operations, this deployment workflow prematurely halts, returning an "Insufficient disk space" error. This behaviour occurs because the VCF 9.x deployment engine natively defaults to validating the greenfield supported storage types and validation checks to vSAN, NFSv3 and VMFS on Fibre Channel (FC).

Resolution

Broadcom is aware of the issue and currently working towards fixing in a future release.

Workaround:

To successfully deploy on datastores that are not supported on greenfield deployment (vSAN, VMFS-FC, NFSv3), satisfy the validation requirements by temporarily add a greenfield supported datastore (e.g. NFSv3-based datastore) to all the ESXi hosts within the target cluster.

Once such storage is registered, the workflow will bypass the "Insufficient disk space" error and proceed to deploy directly onto the designated datastore. (The temporarily added datastore can optionally be unmounted post-deployment).

Additional Information

Refer Supported and Not Supported Configurations to Converge to VCF