"The address <IP> did not belong to any known host" when viewing vApps in Cloud director 10.5

Products

• VMware Cloud Director

Issue/Introduction

Symptoms:

• Issue started after upgrading VCD to 10.5 version.
• Viewing vApp properties displays red banner at the top of the page with the error:

[ UUID ] The address <IP> did not belong to any known host.

• When viewing the VMs inside each vApp, the same error is displayed.
• The VMs work as expected, however EDIT/modify options are greyed out:

• The logs doesn't show any reference to the UUID or the alert. Attempting to access the associated OrgvDC network reports 'operation denied' errors in UI and browser developer tools. In such scenarios, database modifications are required to correct DNS values for OrgvDC network.

Environment

VMware Cloud Director 10.x

Cause

The IP in the alert can be identified as a DNS IP address for an OVDC network, which has a space character at the end of the address resulting in the issue. 

Resolution

To resolve the issue, remove the space character in the DNS fields on the OVDC networks connected to the vApps.
Refer the documentation for how to edit the DNS settings of the OVDC network. In scenarios where OrgvDC network cannot be edited due to the error, database modifications are required to correct DNS values which will require Technical Support assistance. To resolve, please open a Support Request.

Additional Information

Impact/Risks:

Backup solutions fail to take a backup of the affected vApps/VMs.