Adding a Host to a cluster with vVOL Datastore fails at task "Configure vVol Datastore on all the incoming hosts"

Products

• VMware Cloud Foundation

Issue/Introduction

Symptoms:

When attempting to add a host to a cluster with a vVOL Datastore, the workflow fails at the stage:
Configure vVol Datastore on all the incoming hosts with the error:

Storage container vVol Datastore not found in the provider <provider_name> which is registered in vCenter <vCenter_FQDN>

 

On the SDDC Manager, we see the following errors in the domainmanager.log:

2023-02-23T19:55:08.051+0000 ERROR [vcf_dm,021fdafd470e2011,bf23] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-7]  
[2SEDTD] STORAGE_CONTAINERS_NOT_FOUND_FOR_PROVIDER_IN_VCENTER Storage container vVol container not
found in the provider <storage_array> which is registered in vCenter <vcenter_fqdn>
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: 
Storage container vVol container not found in the provider <storage_array> which is registered in vCenter <vcenter_fqdn>
        at com.vmware.evo.sddc.common.services.storage.actions.ConfigureHostVvolDatastoreAction.execute(ConfigureHostVvolDatastoreAction.java:161)
        at com.vmware.evo.sddc.common.services.storage.actions.ConfigureHostVvolDatastoreAction.execute(ConfigureHostVvolDatastoreAction.java:48)
        at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionState.invoke(FsmActionState.java:62)
        at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionPlugin.invoke(FsmActionPlugin.java:159)
        at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionPlugin.invoke(FsmActionPlugin.java:144)

 

 

Environment

VMware Cloud Foundation 4.x

Cause

This error is due to a mismatch in the name of the vVol Container configured in the SDDC Manager UI, and the vVol Container name configured within the vVol provider and presented to the vCenter.

Resolution

1. Retrieve the name of the vVOL Container as presented to the vCenter.
     1.1 Using PowerCLI, connect to the vCenter server, and login with [email protected] credentials

      connect-viserver <vCenter_Server_FQDN> 

     1.2 Get the vVol Container names:

     Get-VvolStorageContainer

Note: In the example above, the randomly generated alpha-numeric IDs are the IOFILTER providers from ESXi hosts. These can be ignored.
The container name presented from the vVOL storage array here is default_storage_container.

2. Login to the SDDC Manager UI and go to the Storage Settings

3. Edit the VASA Provider settings and change the container name to match the output from above.



4. Save the configuration and re-try the workflow.
 

Workaround:
If you are unable to edit the Storage Provider settings via the SDDC Manager UI, please contact VMware GSS for additional assistance.