This issue will be resolved in a future release of Cluster API Provider for VMware Cloud Director (CAPVCD) after v1.3.0.
The available versions of CAPVCD can be seen on the component's GitHub page here,
Releases.
To update Container Service Extension to use a newer CAPVCD release when available the following documentation can be followed,
Update Server Configuration.
Workaround:
To workaround the issue ensure that all VM Placement Policies in Cloud Director have unique names if they are to be used for TKG cluster creation.
The name of an existing VM Placement Policy can be edited as per the Cloud Director documentation here,
Edit a VM Placement Policy in VMware Cloud Director.