VMware Cloud Director
This is due to multiple Solution Landing Zones created with multiple tenants. One of the tenants used for testing the configuration was also deleted.
It is possible to delete the configured Solution Add-On Landing Zone via the Cloud Director OpenAPI and configure it again as per the steps below.
WARNING: The Solution Add-On Landing Zone should only be deleted if there are no solution add-ons present. If add-ons are present then they should be removed before deleting the Solution Add-On Landing Zone. Deleting the add-ons will also require removing all of the instances and capabilities of these add-ons and can only be done if they are not in use.
curl -k -v -X GET "https://<VCD FQDN or IP> /cloudapi/1.0.0/entities/types/vmware/solutions_organization/1.0.0" --header "Accept:application/*;version=38.1" --header "Authorization: Bearer <token>" > /opt/vmware/vcloud-director/data/transfer/apioutput.txt
For each entry, carry out the delete with the below request:curl -k -v -X DELETE "https://<VCD FQDN or IP>/cloudapi/1.0.0/entities/<each URN from the GET request>" --header "Accept:application/*;version=38.1" --header "Authorization: Bearer <token>"
Refer the article for steps to establish an API connection in VMware Cloud Director.