VM Template cannot be deployed to Datastore Cluster from Content Library

Products

• VMware vCenter Server

Issue/Introduction

To Notify the limitations while deploying the VMs from Content library, Datastore Clusters are not supported while deploying VM templates from Content Library.

Symptoms:
Deploy a VM template from Content Library

1. Select the folder > compute > storage           
2. Datastore Clusters are NOT LISTED here
3. Click on any Datastore and proceed NEXT > And BACK again
4. Datastore Clusters are now LISTED.
5. Select the Datastore Cluster.
6. Provide the networking details
7. Deployment is initiated but there appears no task on the vCenter server.

Error in cls.log:

          InvalidArgument (com.vmware.vapi.std.errors.invalid_argument) => {
     messages = [LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
     id = com.vmware.vdcs.vmtx-main.invalid_datastore_id_format,
     defaultMessage = The provided datastore ID urn:vmomi:StoragePod:group-p1395670:bbb5bc65-eaa2-494e-9800-d9692c07e213 is invalid.,
     args = [urn:vmomi:StoragePod:group-p1395670:bbb5bc65-eaa2-494e-9800-d9692c07e213],
     params = <null>,
     localized = <null>
     }],
     data = <null>,
     errorType = INVALID_ARGUMENT
     }

Environment

VMware vCenter Server 7.0.1
VMware vCenter Server 6.5.x
VMware vCenter Server 7.0.2
VMware vCenter Server 6.x
VMware vCenter Server 8.0.x
VMware vCenter Server 7.0.3
VMware vCenter Server 6.7.x
VMware vCenter Server 7.0.0

Cause

The cls backend API expects a datastore ID and it doesn't expect datastore cluster, hence InvalidArgument is reported.

Resolution

Currently there is no resolution.

Workaround:

To avoid this issue, user can do the deployment from outside the Content Library.
Deploy a Virtual Machine from a Template in the vSphere Web Client

Note:
The same set of steps can be followed for vCenter versions 6.7, 7.x, and 8.x.

Additional Information

This issue is being checked by Diagnostics for VMware Cloud Foundation.

The check is as follows:

• Product: vCenter
• Log File: cls.log
• Log Expression Check "com.vmware.vdcs.vmtx-main.invalid_datastore_id_format"