VCF Installer is not ready yet #98
Describe the bugI'm trying to deploy a new Holodeck instance. Version 9.0, using an Online Depot but run into a never ending loop: 05-08-2025 13:39:42 SddcMgmtDomain[23783]: [INFO] VCF Installer is not ready yet, sleeping for 30 seconds ... and so on...any idea? Reproduction steps... Expected behaviorinstallation ends Additional contextNo response |
Replies: 10 comments
|
Can you check if there is enough storage space on both the Holorouter and the physical host on which you are running Holorouter? |
|
Hi, |
|
Solved migrating all the holo VMs to a single host. |
|
Doubled checked that VLANs 0, 10 through 25 and 40 through 58 are allowed on my physical switches. |
|
Are those VLANs allowed on all the interfaces on your physical switches that connect to all the ESX hosts in your vSphere cluster? Is there any IP conflict/subnet overlap with other existing networks in your setup? |
|
Hi, |
|
Checked one more time, if Holorouter and vcfinstaller-a are not on the same host I always get |
|
Interesting! HoloRouter and VCF Installer should be communicating on VLAN 0 (Untagged). Maybe we can troubleshoot it live? |
|
Now I understand: VLAN 0 is not allowed on my physical switches. The network admin did a double check for VLANs 10 through 25 and 40 through 58 but not for VLAN 0. |
|
VCF installer is the only default deployed VM on untagged VLAN in Holodeck. We do have reservations in the DNS server on Holorouter for some optional VMs (such as RDP console if you deploy one and use that reserved IP, etc.) but for any usual Holodeck deployment, VCF installer should be the only one. |
Now I understand: VLAN 0 is not allowed on my physical switches. The network admin did a double check for VLANs 10 through 25 and 40 through 58 but not for VLAN 0.
He cannot allow VLAN 0 on the physical switches so I have to set a rule to force holorouter and VCF installer on the same host.
Last question is: is VLAN 0 (untagged) used for other communications between HOLO VMs? (I hope none)