"Filtering out datastore/storage pod [vcId={id}, moref=datastore-{x}] for subject [type: {id}, URI:{n}] in linked clone filter since it doesnt have the source VM to create linked clone VM" error observed when creating VMs

Products

• VMware Cloud Director

Issue/Introduction

Symptoms:

• This issue occurs either because the datastore’s used storage exceeded the red threshold or linked clone chain of the source Template exceeded the maximum which by default 30.
• When a datastore reaches its red threshold, the virtual machine placement engine stops placing new virtual machines on the datastore except for already-placed imported VMs.
• The maximum chain length allowed is 30 and if this number exceeded Cloud Director automatically will starts provisioning full clone of our virtual machine “Shadow VM” and all the upcoming linked clones will be provisioned from the new Shadow VM.

Environment

VMware Cloud Director 10.x

Resolution

Modify the thresholds of the storage container.

1. Log the Provider portal.
2. From Resource, select Infrastructure Resources.
3. From left panel, select Storage Containers.
4. From right panel, select the datastore..
5. Select Edit and adjust red and yellow thresholds.
   1. By default, the Yellow threshold is 25% of the capacity of the datastore. 
   2. The Red threshold is 15% by default.

 

Confirm the linked clone chain length for vApp Template.

1. Create a user session, see How to establish an API connection VMware Cloud Director
2. Use GET api/vAppTemplate/{id} to find the current value of VirtualDisksMaxChainLength parameter.
   1. https://vcloud.example.com/api/vAppTemplate/vappTemplate-{id}
3. For more information about GET /vAppTemplate/{id}, see
            VMware Cloud Director OpenAPI