The RT VM choose only one datastore in the storage policy and it does not balance cross the datastore

Products

• VMware Cloud Director

Issue/Introduction

• The RT VM on VMware Cloud Director choose only one datastore in the storage policy and it is not balancing across the datastore.
• One datastore in a storage policy is filling up with replication files despite other datastores having more free space.
• Placement Refresh policy is not working in VMware Cloud Director
• In logs, we see that from the cluster always the same datastore with moref=datastore-##### is being selected.
  
  | INFO     | task-service-activity-pool-#### | AlreadyOnValidDatastoreFilter  | Message[INFO]: Placement subject [type:REPLICATION_TRACKING_VM_DISK, URI:c434####-####-####-####-######5454] is already on a valid datastore: moref=datastore-#####. Filtering out all other storage containers. | requestId=UI-1a52####-####-####-####-######668f,request=POST <vcd-url>/api/vApp/vm-27bf####-####-####-####-######4ce4/action/reconfigureVm,requestTime=######,remoteAddress=10.##.###.##:#####,userAgent=Apache-HttpClient/#.#.## (Java/$$.#.##),accept=application/*+xml;version 38.0 vcd=6ab6####-####-####-####-######cf54,task=5b10####-####-####-####-######2462 activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:5b10####-####-####-####-######2462)

Environment

VMware Cloud Director 10.6.x

 

Cause

This issue occurs when VMware Cloud Director doesn't consider the RT VM disk while doing the placement.

Resolution

This issue is resolved in VMware Cloud Director 10.6.1.1  available at Broadcom Downloads

Workaround:

Untag the storage policy tag from the datastore in question so that it gets filtered out initially, allowing other datastores to be selected based on the policy.