Datacenter or Availability Zone Dropdown is Empty When Deploying a Foundation in Tanzu Hub
search cancel

Datacenter or Availability Zone Dropdown is Empty When Deploying a Foundation in Tanzu Hub

book

Article ID: 453805

calendar_today

Updated On:

Products

VMware Tanzu Application Platform VMware Tanzu Platform - Hub

Issue/Introduction

When attempting to deploy a new foundation in Tanzu Hub, the "Datacenter" or "Availability Zone" (AZ) dropdown menus appear blank or do not populate with expected options, preventing the deployment from proceeding.

Symptoms:

  • Blank dropdown menus for Datacenter or AZ fields during the foundation deployment workflow.
  • No visible options available to select, even after selecting a VCF instance.
  • Errors may be visible in browser console or backend graphql-rest-provider-service logs, such as: Unable to parse entityId.

Environment

  • Tanzu Hub (all versions 10.x, specifically reported in 10.4.x)
  • Tanzu Platform Core / Tanzu Foundation

Cause

These configuration fields rely on inventory data collected by the Tanzu Hub collector. The dropdowns remain empty if the capability collection process from the Tanzu Network is incomplete, if the VCF instance is not fully connected, or if the API token used for synchronization has expired or lacks sufficient permissions.

Resolution

To resolve this issue, perform the following troubleshooting steps to ensure the inventory data is correctly synchronized:

  1. Verify VCF Instance Connection:

    • Navigate to Administration > VCF Instances in the Tanzu Hub UI.
    • Verify that the VCF instance status is Connected.
    • If the instance is not connected, re-establish the connection and allow time for the resource collection task to process.

  2. Force a Capability Re-sync:

    • Navigate to the Tanzu Network configuration settings within Tanzu Hub.
    • Re-submit the Tanzu Network API token to trigger a fresh synchronization of capabilities.
    • Ensure that the "Collect capabilities" workflow completes successfully.

  3. Investigate Connectivity (If Issue Persists):

    • If the fields remain blank after a successful re-sync, check the graphql-rest-provider-service logs for connectivity errors between the Hub deployment and the foundation endpoint (e.g., TLS hostname verification issues or 404 errors during inventory API calls).
    • Gather a support bundle and HAR files from the deployment attempt for further analysis if logs indicate persistent failures.

Additional Information

Related articles:

Powered by Wolken Software