Validate NSX install image is available fails

[MarkHargreaves]

I deployed the holorouter, four hosts for management domain, three hosts for workload domain to a B200 M5 blade with 768GB RAM (OSA). 

I worked through the vcf installer issues (change depot status to Success).  Depot configures. 

I downloaded the 9.0 binaries via vcf installer. After validation was successful, I modified $config.state for the VcfInstallerBundle to Success and restarted the script. This started the deployment workflow in the vcf installer. 

The deployment gets to 29% and fails on "Validate NSX install image is available."

This was a 9.0 deployment, but I downloaded the binaries for 9.0.1.0.24952111 that was being requested and reran the deployment.  This failed as well.

I deleted the lab including the holorouter.

I rebuilt the lab and this time I used 9.0.1 binaries. 

Once it hit 29%, I got the above error again.  The reference token changes each time, but I am not sure where to track that.

The binaries are downloaded successfully per the vcf installer. 

I have gotten the same error for both 9.0 and 9.0.1, each time using the version specific installer ova and esx image.

Has anyone run into this error or know of a work around?

Thanks!

[Mariusz Narloch]

had same issue, used local depo. Today starting with online downloading by token. 

[Thomas Miller]

Same issue, I'm running thru the 9.0.0 installer so I can learn to upgrade to 9.0.1.  Not sure why its looking for nsx 9.0.1 in a 9.0.0 install.  Like you I downloaded 9.0.1 same result, re-downloaded 9.0.0 of nsx as well with same result. I'm using the vcf installer on 3 physical host.

[MarkHargreaves]

@Mariusz Narloch

Thanks for the response.  I deployed the offline depot and had the same issue.

@Thomas Miller

Thanks for confirming the same issue.

As of now I have tried the following

• Online depot
  • download 9.0 binaries
  • download NSX 9.0.1 binaries
• Redeploy online depot
  • download 9.0.1 binaries
• Offline Depot
  • download 9.0 binaries
• Redeploy offline depot
  • download 9.0.1

So far all roads have lead to NSX Install Image validation error for 9.0.1 binaries.  

[Thomas Miller]

Hi Mark,

I started over and blew everything away including the host.  This time I chose 901 and everything installed successfully.  Not sure what's up but why would VCF 900 installer want NSX 901?  I'd like to install VCF 900 so I can go through the upgrade to 901, kinda the point right, learning.  I just installed VCF 901 to see if it had the same issue but it worked.  I'm going to keep searching for a solution because I would like to start with VCF 900

[vidar berg+ingebrigtsen]

Its a bug in 9.0, with the manifest that refers to the wrong  NSX file. Its a vcf issue, not holodeck.

Installing 9.0.1 works because it doesn’t have the bug with the manifest.

A kb will be released about this, but  in the interim, check out vmnic.com that has posted a  workaround from VMware. 

[Atif_YNI]

This may not be related but I had issues with using 9.0.1 binaries. 

I was finally able to track down the 9.0 binaries for all.

I am using an offline depot. 

Still had package issues but then I realized that I still had 9.0.1 binaries uploaded to the holorouter and 9.0.0 binaries in the offline depot.

I also had the metadata in the PROD folder from the 9.0.1

I redeployed the router and uploaded 9.0.0 binaries to it. Uploaded all 9.0 binares to the offline depot including the metadata and it few from there for me. 

It completed successfully.

[Dhruv Tyagi]

Please use VCF Installer 9.0.1.0 instead of VCF Installer 9.0.0.0 to deploy VCF 9.0.0.0 as updated in the official BOM (Bill of Materials) provided in the VCF documentation here: https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-0/release-notes/vmware-cloud-foundation-90-release-notes/vmware-cloud-foundation-bill-of-materials.html and try the deployment from scratch again.

[Thomas Miller]

I used the same 901 installer with the same error trying to install VCF 900

As a follow-up; Started over again with the installer 900 but this time with the fix listed here vmnic.com.

It worked, I'm running VCF 900 installed with installer 900 with the fix.  901 installer exhibited same error.  The whole goal is to start with 900 and upgrade to 901.  That's next

[MarkHargreaves]

@Thomas Miller

vmnic.com is the way. Great find!

Thanks to all who provided input on this