Validate NSX Install Image is Available Validate NSX Install Image is Available
NSX install image validation failed for NSX Version - 9.0.1.0.24952111 Remediation: Please download NSX install image with Version - 9.0.1.0.24952111 Reference Token: J####E
Product NSX_T_MANAGER install image not found for version 9.0.1.0.24952111.
Remediation: Ensure that the install image for product NSX_T_MANAGER with version 9.0.1.0.24952111 is downloaded and available
DEBUG [vcf_dm,6######################9,b102] [c.v.e.s.o.d.OrchestratorDissemblers,http-nio-127.0.0.1-7200-exec-2] The processing context being built is {"processingStateId":"ac10####-####-####-####-########0000","processingStateName":"VcfInstallerValidation_onFirstStart","refId":"VcfInstallerValidation_onFirstStart____0__","executionId":"86ba####-####-####-####-########5eb7","sddcId":"mgmt","status":"INITIALIZED",
ERROR [vcf_dm, 6######################4, 81f3] [c.v.e.s.o.model.error.ErrorFactory, dm-exec-18] [2####P] NSXT_INSTALL_IMAGE_VALIDATION_FAILED NSX install image validation failed for NSX Version - 9.0.1.0.24952111
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: NSX install image validation failed for NSX Version - 9.0.1.0.24952111
at com.vmware.vcf.clustermanager.fsm.actions.ValidateNsxtInstallImage.execute(ValidateNsxtInstallImage.java:105)
at com.vmware.vcf.clustermanager.fsm.actions.ValidateNsxtInstallImage.execute(ValidateNsxtInstallImage.java:38)
Caused by: java.lang.RuntimeException: Retriable operation 'Retrieving install image for NSX with version 9.0.1.0.24952111' failed to complete after 5 retries.
Caused by: com.vmware.evo.sddc.common.services.error.SddcManagerServicesIsException: Product NSX_T_MANAGER install image not found for version 9.0.1.0.24952111.
VCF Installer 9.0.1
This is a known issue and is fixed in future VCF installer release
To proceed with the deployment follow the below workaround
Workaround 1:
This workaround if applied on the VCF installer it will only work if implemented before starting a new VCF Deployment. If a deployment has already been initiated, the workaround will work only if executed from the SDDC Manager.
fix_manifest.sh and vcfManifestWithout901New.json files attached to this article. chmod +x fix_manifest.sh
./fix_manifest.sh '<admin-local-password>' vcfManifestWithout901New.json
Workaround 2:
This Workaround needs to be followed while not initiating the installer wizard from scratch
echo vcf.vault.http-access=true >> /etc/vmware/vcf/domainmanager/application.properties && systemctl restart domainmanager
Wait a minute or so for the domainmanager service to restart
curl -X GET http://localhost/domainmanager/internal/vault/<execution ID identified from domainmanager.log> | json_pp > /tmp/workflow.json
Sample
curl -X GET http://localhost/domainmanager/internal/vault/86ba####-####-####-####-########5eb7 | json_pp > /tmp/workflow.json
curl -H 'Content-Type:text/plain' -X PUT http://localhost/domainmanager/internal/vault/86ba####-####-####-####-########5eb7 -d @/tmp/workflow.json