Constant "Couldn't get bundle details. Trying again after 10 seconds #119
-
|
So, I found I was having a capacity issue on my standalone host. I had two different LUN's and needed to combine them. New-HoloDeckInstance -Version "9.0.2.0" -InstanceID gray -vSANMode ESA -NsxEdgeClusterMgmtDomain -DeployVcfAutomation -DepotType "Online" Everything remained the same on the Holo Router, all of the binaries are there for 9.0.2. However, now it keeps giving the following: 28-04-2026 22:54:49 SetHoloDeckConfig[2283]: [INFO] Updating the Global Config, ConfigKey: vSANMode, ConfigValue: ESA I have tried stopping and restarting, but get the same results. Anyone else encountered or have a fix? |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 2 replies
-
|
When you log in to VCF Installer and navigate to the depot page, do you see the bundle details populated? If not, right click on the browser > Inspect element > Network tab and look for the sddcs API call and see if VCF Installer is unable to get the bundle meta data. |
Beta Was this translation helpful? Give feedback.
-
|
The weird thing is I cannot get to it from the jump server I put in the environment. Both can ping the same gateway. The jump server can pull up all of the ESX host created, just not anything to do with the installer. I even tried restarting some services. Trace route 
|
Beta Was this translation helpful? Give feedback.
-
|
What about accessing the VCF Installer UI from webtop? |
Beta Was this translation helpful? Give feedback.
-
|
It says the depot is online, but nothing downloaded. 
|
Beta Was this translation helpful? Give feedback.
-
|
In addition, I deleted everything, including the holorouter. Redeployed, and have the same results. |
Beta Was this translation helpful? Give feedback.
-
|
Same situation here... I was able to download by SDDC manager but the Holodeck still has the same message |
Beta Was this translation helpful? Give feedback.
-
|
Looks like you're hitting #122 |
Beta Was this translation helpful? Give feedback.
-
|
Resolved |
Beta Was this translation helpful? Give feedback.
-
|
Implemented the workaround. Works great. Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
So, spoke too soon. I implemented the workaround and walked away after it started. Checked it after work today and have this error on the installer: |
Beta Was this translation helpful? Give feedback.
-
|
What's the workaround you applied? Changed the -eq 7 to -ge 7? That would download the patch file as well causing this issue. Better way to solve this is to change "9.0.2.0.*" to "^9.0.(0|2).0.\d+$". Then you will have to delete the instance and deploy again because your current installer already has the bundles downloaded including the patch bundles |
Beta Was this translation helpful? Give feedback.
Looks like you're hitting #122