Workload Domain creation fails with "Failed to validate domain spec" and "Failed to retrieve component binary" in VCF 9
search cancel

Workload Domain creation fails with "Failed to validate domain spec" and "Failed to retrieve component binary" in VCF 9

book

Article ID: 439546

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

  • When you attempt to create a Workload Domain in VMware Cloud Foundation (VCF), the process fails with the following errors displayed in the user interface:
    • "Failed to validate domain spec"
    • "Failed to retrieve component binary"



  • Review of the /var/log/vmware/vcf/domainmanager/domainmanager.log on the SDDC Manager appliance reveals errors while retrieving vCenter Server and NSX installation binaries.
    YYYY-MM-DDTHH:MM:SSZ INFO [vcf_dm, ed#######7, b718] [c. v. v. v. v. DomainSpecValidator, http-nio-127.0.0.1-7200-exec-3] Completed the validation of the DomainSpec
    YYYY-MM-DDTHH:MM:SSZ ERROR [vcf_dm, ed#######7, b718] [c. v. v. v.utils. DomainCreationUtil, http-nio-127.0.0.1-7200-exec-3] Domain Creation Spec validations for SKU EMS failed with errors [FAILED TO_RETRIEVE_COMPONENT BINARY, FAILED TO RETRIEVE COMPONENT BINARY].
    YYYY-MM-DDTHH:MM:SSZ ERROR [vcf_dm, ed#######7, b718] [c.v. v.v. c. v1. DomainController, http-nio-127.0.0.1-7200-exec-3] Failed to create domain com. vmware. evo. sddc. common. core. error .CompositeInvalidInputException: Failed to validate domain spec

    YYYY-MM-DDTHH:MM:SSZ INFO [vcf_dm, ed#######7, b718] [c. v.e. s.c. s. a. i. ImageManagementServiceAdapterImpl, http-nio-127.0.0.1-7200-exec-3] Got VCENTER product version for new Workload Domain: 9.0.2.0.25148086
    YYYY-MM-DDTHH:MM:SSZ INFO [vcf_dm, ed#######7, b718] [c.v. v. v. v. DomainSpecValidator, http-nio-127.0.0.1-7200-exec-3] Successfully fetched VC version 9.0.2.0.25148086
    YYYY-MM-DDTHH:MM:SSZ INFO [vcf_dm, ed#######7, b718] [c. v. v. v. v. DomainSpecValidator, http-nio-127.0.0.1-7200-exec-3] Failed to get install image for component VCENTER, version 9.0.2.0.25148086

    YYYY-MM-DDTHH:MM:SSZ INFO [vcf_dm, ed#######7, b718] [c. v.e.s.c. s. a. i. ImageManagementServiceAdapterImpl, http-nio-127.0.0.1-7200-exec-3] Got NSX T MANAGER product version for new Workload Domain: 9.0.2.0.25150386
    YYYY-MM-DDTHH:MM:SSZ INFO [vcf_dm, ed#######7, b718] [c. v.e. s.c. s.NsxtVersionServiceImpl, http-nio-127.0.0.1-7200-exec-3] Fetched NSX BOM version 9.0.2.0.25150386 with provided NSX VIP FQDN <NSX-FQDN>
    YYYY-MM-DDTHH:MM:SSZ DEBUG [vcf_dm, ed#######7, b718] [c. v. v. v. v. DomainSpecValidator, http-nio-127.0.0.1-7200-exec-3] Successfully fetched NSX version 9.0.2.0.25150386
    YYYY-MM-DDTHH:MM:SSZ ERROR [vcf_dm, ed#######7, b718] [c. v. v. v. v. DomainSpecValidator, http-nio-127.0.0.1-7200-exec-3] Failed to get install image for component NSX_T_MANAGER, version 9.0.2.0.25150386
    com. vmware. evo. sddc. common. services. error. SddcManagerServicesIsException: Product NSX_T_MANAGER install image not found for version 9.0.2.0.25150386
  • Furthermore, connection tests to the offline depot within the VCF Operations UI return a "Depot Unknown Error" when communicating over port 80.

 

Environment

  • VCF 9.x
  • VCF Operations 9.x

Cause

The required installation binaries are absent from the configured offline depot. Additionally, VCF Operations cannot connect to the offline depot to retrieve these binaries due to an incorrect port configuration (using Port 80 instead of the required Port 443).

Resolution

To resolve this issue, you must seed the depot and correct the connection settings:

  1. Download the required VCF installation bundles to the offline depot using the VCF Download Tool. Refer Download Install Binaries to an Offline Depot.
  2. Modify the offline depot port configuration in VCF Operations from port 80 to port 443.
    1. Log in to the VCF Operations UI using an account with Administrator privileges.
    2. Navigate to the Fleet Management section by clicking Fleet Management > Lifecycle in the left navigation pane.
    3. Select VCF Instances to view the managed instances.
    4. Click the name of the specific VCF Instance where the Workload Domain creation is failing.
    5. Click the Depot Settings tab.
    6. Locate the Offline Depot configuration pane and click Edit to modify the connection parameters.
    7. Update the connection string to enforce secure communication over port 443
    8. Verify that the required authentication credentials for your internal offline depot web server are populated.
    9. Click Save or Validate to commit the changes. The system will test the connection to the offline depot over port 443.
  3. Initiate the download for the vCenter Server and NSX installation binaries through the VCF Operations UI.
    1. Navigate to the Fleet Management section by clicking Fleet Management > Lifecycle in the left navigation pane.
    2. Select Bundle Management (or navigate to your specific VCF Instance and select the Updates/Bundles tab).
    3. Locate the Available Bundles section. The system will poll the connected offline depot and display a list of binaries that are missing locally but available in the depot.
    4. Locate and Select the specific vCenter Server and NSX installation binaries (Confirm the required version from domainmanager.log. For ex. In this scenario version 9.0.2 binaries are missing).
    5. Click the Download button adjacent to each respective bundle.
  4. Re-attempt the Workload Domain creation once the binary downloads are complete.

Additional Information

Download Install Binaries to an Offline Depot

Powered by Wolken Software