You need to allow HTTP in config file and change "InProgress" in .json file to trick installer to next step.
https://williamlam.com/2025/06/using-http-with-vcf-9-0-installer-for-offline-depot.html
Original Message:
Sent: Jul 03, 2025 09:33 AM
From: Jerard Chilton
Subject: Holodeck v9 - Offline bundle depot NSX failed to download
Not sure i understand what you mean. The install has stopped mid deployment - the nested hosts and VCF Installer has been deployed. When I import the cofig into a new pwsh and run the came command i.e. New-HolodeckInstance ****, it exits stating a yaml already exists. See pic attached.
Is there a retry command? Do i need to remove the complete instance and start again?
Original Message:
Sent: Jul 03, 2025 08:49 AM
From: G Kastelic
Subject: Holodeck v9 - Offline bundle depot NSX failed to download
Just re-run the same command.
Original Message:
Sent: Jul 03, 2025 05:59 AM
From: Jerard Chilton
Subject: Holodeck v9 - Offline bundle depot NSX failed to download
What are the commands in pwsh to retry the deployment; just thinking ahead for when i fix the NSX download issue. Do i import the config instance again and run a NewInstance command??? Or do i log into the VCF INstaller UI and follow the wizard?
Original Message:
Sent: Jul 02, 2025 03:53 PM
From: Jerard Chilton
Subject: Holodeck v9 - Offline bundle depot NSX failed to download
Trying to spin up the Holodeckv9 and it fails using the Offline depot. I've downloaded the offline-depot OVA, deployed it and used a valid token to connect to the Broadcom URL.
Took 3.5hrs to download binearies but when I point the VCF Installer to the offline depot and try to deploy a new instance it fails to download NSX.
Pic attached. Any ideas why the offline depot would fail to pull the correct NSX binary? Anyone else seen this? All the other binaries were pulled down.
Is there a simple fix or do i need to use the VCF download tool on a Linux box and manually transfer the correct binary?