This is a known issue affecting VMware vRealize Automation (formerly known as vCloud Automation Center) 5.1 and 5.2.
A resolution for this issue is being evaluated for inclusion in a future release.
To work around this issue, remove the Location for all Compute Resources that do not contain Resource Reservations.