Content Library fails to create when target datastore contains a space in VMware Cloud Foundation for Service Providers

Products

• VMware Cloud Foundation

Issue/Introduction

Symptoms:

• The datastore being used for the new library contains a space in it’s name then the Create Content Library process fails.
• The error given is “The specified parameter was not correct: The provided storage backing xxxxx xx for library xxxxx-xxxx-xxxx-xxx is invalid.”.
• For example, if a second vSAN cluster has been created and the default name “vsanDatastore (1)” was used for the datastore.
• Task events observed similar to:    

Event: Deletion of file or directory [vsanDatastore (1)] /contentlib-xxxxxx-xxxxx-xxxx-xxxxx from vsanDatastore (1) was initiated from 'cl/[email protected]' and completed with status 'Failure'
 

Environment

VMware Cloud Foundation 3.0.x
VMware Cloud Foundation 2.x

Cause

If a unique datastore name is not used in the API specification at datastore creation, content library creation will fail with similar symptoms as above. 

Resolution

• Specify a unique datastore name without spaces in the name when creating a datastore will prevent this issue from occurring.
• If datastores have already been created in production environment, please see workaround section. 

 

Workaround:

 

1.  Rename the target datastore to a name which does not contain a space then repeat the Content Library creation process.

2.  Rename target datastore to original name to avoid potential SDDC manager database issues when running workflows. 

 

Additional Information

* Vmware Cloud Foundation - Guidance on Supported Customizations. 
https://docs.vmware.com/EN/VMware-Cloud-Foundation/2.3.1/VMware%20Cloud%20Foundation%20Guardrails.pdf