Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Datastores are not accessible in a VMware vCloud Director Org Virtual DataCenter (2075366)

Symptoms

  • Storage Clusters are available to add to a Provider Org Virtual DataCenter (vDC)  in vCloud Director 5.5.x.
  • After moving a datastore to a Storage Cluster, the datastores are no longer accessible to the Org Virtual DataCenter (vDC) in vCloud Director (vCD).
  • Refreshing Storage Policies on vCenter Server containing the Storage Cluster does not resolve the issue.

Resolution

This issue is resolved in vCloud Director 5.5.2, available at VMware Downloads. For more information, see the vCloud Director 5.5.2 Release Notes.

If you cannot upgrade, you can work around this issue by clearing the Inventory and Property map tables.

Note: This can also be caused if tags are not configured correctly for storage. For more information, see the About Virtual Machine Storage Policies section of vSphere Storage.

To clear the inventory and property map tables:

  1. Stop all Active Cells using the Cell Management Tool, for more information, see Using the Cell Management Tool to shut down a vCloud Director cell (1033575).
  2. Stop the vCD services.

    Note: Repeat steps 1 and 2 for all cells in the vCloud Directory installation.

  3. Run these SQL statements on the vCD database to clean up the inventory tables:

    delete from cluster_compute_resource_inv;
    delete from compute_resource_inv;
    delete from custom_field_manager_inv;
    delete from datacenter_inv;
    delete from datacenter_network_inv;
    delete from datastore_inv;
    delete from datastore_profile_inv;
    delete from dv_portgroup_inv;
    delete from dv_switch_inv;
    delete from folder_inv;
    delete from managed_server_datastore_inv;
    delete from managed_server_inv;
    delete from managed_server_network_inv;
    delete from network_inv;
    delete from resource_pool_inv;
    delete from storage_profile_inv;
    delete from storage_pod_inv;
    delete from task_inv;
    delete from vm_inv;
    delete from property_map;


  4. Start the services on one vCloud Director cell and run it for approximately 5 minutes.
  5. Start the services on all other cells.

See Also

Update History

09/11/2014 - Added links to vCloud Director 5.5.2 which resolves the issue

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 7 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 7 Ratings
Actions
KB: