Getting error "Product NSX_T_MANAGER install image not found for version 9.0.1.0.24952111" when deploying VCF 9.0.0

Products

• VCF Operations

Issue/Introduction

• VCF 9.0.0 deployment fails at error "Product NSX_T_MANAGER install image not found for version 9.0.1.0.24952111. Remediation: Make sure install image for product NSX_T_MANAGER with version 9.0.1.0.24952111 is downloaded and available. Reference Token: C0HV71"


• VCF Installer version 9.0.1 is used as the installer appliance.

Environment

VMware Cloud Foundation 9.0.0

Cause

This issue occurs when VCF Installer 9.0.1 is used to deploy VCF 9.0.0.

Resolution

The recommendation is to use VCF installer 9.0.1 to install VCF 9.0.1 instead of installing 9.0.0

In case you wish to keep the same VCF Installer 9.0.1 to install VCF 9.0.0, the below workaround should help you get past the NSX image not found error.

Please ensure that before you implement the steps given below, a snapshot of the VCF Installer appliance is taken. 

• Automatic method:

1. Download both fix_manifest.sh and vcfManifestWithout901New.json files attached to this article.
2. Using a file transfer utility, upload both files to the VCF Installer appliance.
3. SSH to the VCF Installer (or SDDC Manager depending on the scenario)
4. Change to root using the below command.
   
   su


5. Navigate to the location of the uploaded files and update the file permissions:
   
   chmod +x fix_manifest.sh


6. Run the below command to execute the script.
   
   ./fix_manifest.sh '<admin-local-password>' vcfManifestWithout901New.json

The VCF 9.0.0 deployment can now be retried. 

• Manual Method:

1. Configure Depot Settings on VCF Installer as normal documented process (offline or online).
2. SSH to the VCF Installer (or SDDC Manager depending on the scenario)
3. Change to root using the below command.
   
   su 
   
   
4. Now copy the attached json file under /home/vcf/vcfManifestWithout901.json (Note: this file can be produced locally as well by modifying the /nfs/vmware/vcf/nfs-mount/metadata/vcfManifest.json and removing the element describing the 9.0.1 release (lines 1707-2191). Be careful to not break the syntax of the json file when deleting manually the element and also make sure to save a copy of the original vcfManifest.json file)
   
   
5. Execute the below commands.
   
   psql -h localhost -U postgres lcm -c "DELETE FROM manifest;"

TOKEN=$(curl -H 'Content-Type:application/json' https://localhost/v1/tokens -d '{"username" : "admin@local","password":"#####"}' -k | jq -r '.accessToken')

curl -k -H 'Content-Type: application/json' -H "Authorization: Bearer $TOKEN" -X POST https://localhost/v1/manifests -d "@/home/vcf/vcfManifestWithout901New.json"
   
   
6. Post the above step, the 9.0.1 release will not be shown in the UI and deployment with 9.0.0 BOM should succeed. After making this change, if you want to deploy 9.0.1 on the same VCF 9.0.1 appliance, follow the same steps but on step 4 you use the original json file and not the modified one.