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

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

book

Article ID: 338405

calendar_today

Updated On:

Products

VMware Cloud Foundation VMware vCenter Server

Issue/Introduction

Symptoms:
  • The datastore being used for the new Content Library contains a space in it’s name.
  • You see similar error messages as:
The specified parameter was not correct: The provided storage backing xxxxx xx for library xxxxx-xxxx-xxxx-xxx is invalid.
  • An example, If a second vSAN cluster has been created and the default name “vsanDatastore (1)” was used for the datastore.
  • Task events in vCenter Web Client 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'


Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.


Environment

VMware vCenter Server 6.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

To ensure that this specific issue is not faced, specify a unique datastore name without spaces in the name when creating a datastore will prevent this issue from occurring.

If the datastore has already been created, please see the below Workaround section.

 



Workaround:

To workaround the failure with an existing datastore, please follow the below steps:

  1. Rename the target datastore to a name which does not contain a space.
  2. Restart the Content Library creation task. 


 


Additional Information

Vmware Cloud Foundation - Guidance on Supported Customizations. 

 


Powered by Wolken Software