VCF installation fails during NFS Datastore Configuration with an error message that reads, "NFS datastore <datastore name> with remote server <NFS datastore IP address> and remote path </datastore path> not found on host <ESX FQDN>, with a remediation message that suggests "Ensure that the datastore is mounted on the host".
/var/log/vmware/vcf/domainmanager/domainmanager.log
YYYY-MM-DDTHH:MIN:SEC INFO [vcf_dm,690916c619aa441a7935069e8d27f98e,0b02] [c.v.e.s.c.c.v.vsphere.VsphereClient,dm-exec-4] Successfully logged in to <ESX FQDN>YYYY-MM-DDTHH:MIN:SEC DEBUG [vcf_dm,690916c619aa441a7935069e8d27f98e,0b02] [c.v.e.s.c.c.v.vsphere.VcManagerBase,dm-exec-4] Finding host with fqdn <ESX FQDN>YYYY-MM-DDTHH:MIN:SEC DEBUG [vcf_dm,690916c619aa441a7935069e8d27f98e,0b02] [c.v.e.s.v.a.ValidateNfsConfigurationAction,dm-exec-4] Excluding host <ESX FQDN> with VMKernel IPs [10.0.0.1]YYYY-MM-DDTHH:MIN:SEC DEBUG [vcf_dm,690916c619aa441a7935069e8d27f98e,0b02] [c.v.e.s.v.a.ValidateNfsConfigurationAction,dm-exec-4] Validating existing NFS datastore <NFS Datastore Name> on ESXi host <ESX FQDN> used for running the VCF Installer applianceYYYY-MM-DDTHH:MIN:SEC INFO [vcf_dm,690916c619aa441a7935069e8d27f98e,0b02] [c.v.e.s.c.c.v.vsphere.VsphereClient,dm-exec-4] Successfully logged in to <ESX FQDN>YYYY-MM-DDTHH:MIN:SEC INFO [vcf_dm,690916c619aa441a7935069e8d27f98e,0b02] [c.v.e.s.c.c.v.vsphere.VcManagerBase,dm-exec-4] Found 0 NFS datastores on vCenterYYYY-MM-DDTHH:MIN:SEC DEBUG [vcf_dm,690916c619aa441a7935069e8d27f98e,0b02] [c.v.e.s.c.v.util.ResponseUtil,dm-exec-4] Build validation response: {"errorCode":"NFS_DATASTORE_NOT_FOUND.error","arguments":["<NFS Datastore Name>","10.0.0.2","/<NFS Datastore Name>","<ESX FQDN>"],"context":{"severity":"ERROR","validation.taskId":"####-####-####-####-#######"},"message":"NFS datastore \u0027\u0027{0}\u0027\u0027 with remote server {1} and remote path {2} not found on host {3}","remediationMessage":"Ensure that the datastore is mounted on the host."}
VCF 9
During the VCF bringup process, when the parameter useExistingDeployment is set to true and the datastore type is specified as NFS, the exact NFS datastore referenced in the bringup specification is expected to be mounted and accessible on the ESXi host hosting the VCF Installer virtual machine.
The deployment failure being observed here is observed in cases where this required NFS datastore is missing, not properly mounted on the specified host or doesn't have the same "datastoreName", "serverName" or "path" as specified in the bringup specification.
To successfully proceed with a VCF bringup using useExistingDeployment set to true and a datastore type of NFS, the user must ensure the following prerequisites are met before initiating the deployment: