Symptoms:
Found 2 powered-on VMs with FQDN hostname.corp.local, should be 1.
2023-06-30T11:15:32.055+0000 DEBUG [vcf_om,ee75f942c2d6cf7a,12df] [c.v.v.p.helper.GuestProgramService,om-exec-12] Fetched list of powered on virtual machines [ManagedObjectReference: type = VirtualMachine, value = vm-14,
serverGuid = 12f0da5f-b7b5-4ceb-b45d-1d634ba79e8b, ManagedObjectReference: type = VirtualMachine, value = vm-74, serverGuid = 12f0da5f-b7b5-4ceb-b45d-1d634ba79e8b] whose DNS name prefixes FQDN hostname.corp.local from cluster PROD-Cluster-1
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
VMware Cloud Foundation 4.x
While fetching the list of virtual machines whose DNS name prefixes the FQDN, we are also returning virtual machines with an empty or blank DNS value.
This has been resolved in VMware Cloud Foundation 4.5.1 and 5.0
Workaround:
Following steps make changes to the Postgres database. Always ensure recent backups are available prior to making any database edits.
Use the following steps as a workaround:
/opt/vmware/vpostgres/current/bin/psql -d VCDB -U postgres
select * from vpx_vm where id='74';
select * from vpx_vm where id='14';
update vpx_vm set dns_name='Relevant_FQDN' where id='74';
update vpx_vm set dns_name='Relevant_FQDN' where id='14';