Quantcast
Channel: Veeam Support Knowledge Base
Viewing all articles
Browse latest Browse all 4362

Missing vCenter entries in settings for vCloud Director

$
0
0
KB ID: 4193
Product: Veeam Backup & Replication, Veeam Cloud Connect

Challenge

When adding/editing vCloud Director Server in Veeam Backup & Replication the vCenter Servers list is missing vCenter entries.
empty vc list
The console log contains the following errors:
Error Failed to retrieve VC info
Error Failed to parse GUID from string 
Error Guid should contain 32 digits with 4 dashes

Cause

This is related to a known issue in VMware Cloud Director version 10.2.1 and earlier. API calls to retrieve the vCenter Server information result in the VMware Cloud Director API incorrectly returning a URL instead of the expected UUID.

This can be verified using either of the following methods:

Verify using SQL query aginst vCloud Director database
 execute the following SQL query against the vCloud Director database:
select name, uuid from virtual_center;
Example output:
name   | uuid
----------------------------------------------
testvc | 0034117e-b58b-4aca-8f96-50774aba6d1f
newvc  | https://<url>/sdk
In this example, the first entry has a UUID as expected, and the second entry is a URL in the UUID field.
Verify issue using vCloud Director API

Use a GET request to retrieve the representation of a registered vCenter server.

GET /admin/extension/vimServer/{id}
(Click for more information.)

Example output:

Correct UUID format:

< vmext:Uuid > D9658206-D7AA-4D80-8E38-5328A39ABDD4 </ vmext:Uuid >

Problematic output:

< vmext:Uuid > https://vcloud.prod.local </ vmext:Uuid >

Solution

VMware has corrected this in vCloud Director 10.2.2 and 10.3.

The fix is preventative only and will not retroactively correct invalid entries.

To resolve this error and update the invalid entries, the following steps must be performed:

  1. Upgrade vCloud Director (together with its database) to 10.2.2, 10.3, or later.
  2. Reconnect the affected vCenter in vCloud Director.
    This action will update the invalid database entry.

Repeat Step 2 for each vCenter affected by this issue.

If the issue persists after performing the steps listed above and the database still contains non-GUID entries in the UUID field, please get in touch with VMware support.

More information

VMware BugId: 2680344

Viewing all articles
Browse latest Browse all 4362

Trending Articles