Building a new cluster into an existing workload domain failed at: validate host(s) have read/write access to NFS server stage
search cancel

Building a new cluster into an existing workload domain failed at: validate host(s) have read/write access to NFS server stage

book

Article ID: 369614

calendar_today

Updated On:

Products

VMware SDDC Manager

Issue/Introduction

Symptoms:

  • Deploying a new cluster failed with the following error: Failed to skip failed ESXi hosts ESXi_FQDN

 

  • domainmanager.log contains errors similar to the excerpt below:
    2024-06-05T12:33:11.657+0000 DEBUG [vcf_dm,a07e9d8a51624fdf,d193] [c.v.v.c.f.p.a.i.ValidateHostNfsDatastoreAction,dm-exec-13] Datastore nfs_datastore_name is not present on ESXi Host ESXi_FQDN_name1
    2024-06-05T12:33:11.657+0000 DEBUG [vcf_dm,a07e9d8a51624fdf,d193] [c.v.e.s.c.c.v.vsphere.VsphereClient,dm-exec-13] Destroying 1 open views
    2024-06-05T12:33:11.662+0000 ERROR [vcf_dm,a07e9d8a51624fdf,d193] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-13] [MEIVSA] VSPHERE_SKIP_FAILED_ESXI_HOSTS_FAILED Failed to skip failed ESXi hosts ESXi_FQDN_name1, ESXi_FQDN_name2

    com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Failed to skip failed ESXi hosts ESXi_FQDN_name1, ESXi_FQDN_name2
    at com.vmware.vcf.common.fsm.plugins.action.impl.ValidateHostNfsDatastoreAction.skipFailedHosts(ValidateHostNfsDatastoreAction.java:319)
    at com.vmware.vcf.common.fsm.plugins.action.impl.ValidateHostNfsDatastoreAction.execute(ValidateHostNfsDatastoreAction.java:140)
    at com.vmware.vcf.common.fsm.plugins.action.impl.ValidateHostNfsDatastoreAction.execute(ValidateHostNfsDatastoreAction.java:51)
    at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionState.invoke(FsmActionState.java:62)

 

 

Environment

VMware Cloud foundation 5.x
VMware Cloud Foundation 4.x

Cause

This issue is caused by the mismatched NFS storage configuration during the installation of the ESXi.

Resolution

The customer engaged with their internal storage team to fix the mismatched NFS storage configuration on the ESXi.


After the resolution of the storage configuration issue, the deployment of a new cluster was successful.