This issue is resolved in vCloud Director 5.1.2, available at
VMware Downloads. For more information about this version, see the
vCloud Director 5.1.2 Release Notes.
To work around this issue when you do not want to upgrade, manually remove the stale entries from the
Resource_Assignment table in the vCloud Director database.
To manually remove stale entries from the vCloud Director database:
- Back up the vCloud Director database.
- Connect to the vCloud Director database.
- To verify stale entries for the VLAN, run this command:
SELECT * from resource_assignment where resource_uri = 'urn:vlanid:xxx';
Where xxx is the affected VLAN ID.
Note: The output returns only one result as the VLAN ID is unique.
- To verify stale entries for the portgroups associated with that VLAN, run this command:
Note: Depending on your environment, you may have multiple entries for the VLAN
SELECT * from resource_assignment where resource_uri in (
SELECT owner_uri from resource_assignment where resource_uri = 'urn:vlanid:xxx');
- Verify if the affected portgroups or VLANs are in use in vCloud Director.
- If the portgroups or VLANs are not in use, proceed to step 6 to delete the entries in the vCloud Director database.
- If the portgroups or VLANs are in use, they may have been recreated with the same name.
- To delete the VLAN:xxx entry, run this command:
DELETE from resource_assignment where resource_uri = 'urn:vlanid:xxx';
- To delete associated portgroup entries, run this command:
DELETE from resource_assignment where resource_uri in (
SELECT owner_uri from resource_assignment where resource_uri = 'urn:vlanid:xxx');
- To verify that the stale entries are removed, run this command:
SELECT * from resource_assignment where resource_uri = 'urn:vlanid:xxx';