Datastore Name Missing from SDDC Manager Cluster Inventory View - VMware SDDC Manager
search cancel

Datastore Name Missing from SDDC Manager Cluster Inventory View - VMware SDDC Manager

book

Article ID: 453049

calendar_today

Updated On:

Products

VMware SDDC Manager / VCF Installer

Issue/Introduction

This article provides steps for scenarios where Fibre Channel (FC) or vSAN datastores fails to appear in the cluster inventory view within SDDC Manager, even when they are visible and functional in vCenter Server.

Symptoms

  • Navigating to a Workload Domain cluster inventory does not display datastores under the VMFS or vSAN sections.

  • Prechecks for cluster updates fail due to missing primary storage metadata.

  • Datastore names were renamed out-of-band in vCenter Server after the initial workload domain import.

Environment

VMware Cloud Foundation (VCF) 9.x

Cause

SDDC Manager relies on metadata established during the workload domain import. When datastores are renamed or reconfigured in vCenter Server (out-of-band) after the initial discovery, the SDDC Manager database retains stale information, leading to a mismatch that prevents the inventory view from loading correctly.

Resolution

Reconcile the SDDC Manager database with the current vCenter Server inventory by following the below steps:

  1. Revert Datastore Name: Ensure that the datastore name in vCenter Server is reverted to the original name registered during the initial cluster commissioning.

  2. Trigger Inventory Sync:

    • Log in to the SDDC Manager UI.
    • Navigate to Workload Domains > [Select Domain] > Clusters.
    • Select the affected cluster.
    • Initiate the Inventory Sync feature to force a reconciliation of the cluster metadata with vCenter Server.

  3. Verify Inventory: Refresh the Cluster Summary page in SDDC Manager. The vSAN or VMFS datastore should now appear correctly.

  4. License Verification: Navigate to the Licensing section in SDDC Manager. Verify that the vSAN Witness or cluster hosts have the appropriate licenses applied, as the sync often resolves licensing mapping errors created by the database mismatch.

  5. Re-run Prechecks: Once the inventory is displayed, initiate the cluster precheck operation to verify that all alerts regarding missing storage have cleared.

Additional Information