VCF Installer is not ready yet

[miskaste]

Describe the bug

The process stops at the step "Verifying VCF Installer availability" and gets stuck in a loop. When checking from the WEB UI, you can see that all files are available. I tried to repeat the creation of a new instance, but it's the same every time.

7-11-2025 13:40:09 ESXBuild[4246]: [INFO] Adding 'Network adapter 4', Setting up adapter Type to 'VMXNET3'
07-11-2025 13:40:10 ESXBuild[4246]: [INFO] Reconfiguring blue-esx-06a
07-11-2025 13:40:13 ESXBuild[4246]: [INFO] Setting up SCSI Controller type to 'ParaVirtual' and BusSharingMode to 'NoSharing' on blue-esx-06a
07-11-2025 13:40:14 ESXBuild[4246]: [INFO] Requested vSAN Type os 'OSA'
07-11-2025 13:40:14 ESXBuild[4246]: [INFO] Adding a new cache disk of 90GB on blue-esx-06a
07-11-2025 13:40:16 ESXBuild[4246]: [INFO] Adding a new capacity disk 1 of 450GB on blue-esx-06a
07-11-2025 13:40:18 ESXBuild[4246]: [INFO] Adding a new capacity disk 2 of 450GB on blue-esx-06a
07-11-2025 13:40:21 ESXBuild[4246]: [INFO] Marking Hard disk 1 as Virtual SSD on blue-esx-06a
07-11-2025 13:40:23 ESXBuild[4246]: [INFO] Marking Hard disk 2 as Virtual SSD on blue-esx-06a
07-11-2025 13:40:25 ESXBuild[4246]: [INFO] Marking Hard disk 3 as Virtual SSD on blue-esx-06a
...skipping...
08-11-2025 05:44:19 SddcMgmtDomain[4246]: [DEBUG] Start Push-HoloDeckState Function
08-11-2025 05:44:19 SetHoloDeckState[4246]: [DEBUG] after function completion:
08-11-2025 05:44:19 SetHoloDeckState[4246]: [DEBUG] New-HoloDeckInstance SingleSite-a FullStack New-HoloSite-a Deploy-ManagementDomain
08-11-2025 05:44:19 SddcMgmtDomain[4246]: [INFO] Beginning SDDC Management Domain Deployment
08-11-2025 05:44:19 SddcMgmtDomain[4246]: [INFO] Verifying VCF Installer availability
08-11-2025 05:44:21 SddcMgmtDomain[4246]: [INFO] VCF Installer is not ready yet, sleeping for 30 seconds ...
08-11-2025 05:44:53 SddcMgmtDomain[4246]: [INFO] VCF Installer is not ready yet, sleeping for 30 seconds ...
08-11-2025 05:45:25 SddcMgmtDomain[4246]: [INFO] VCF Installer is not ready yet, sleeping for 30 seconds ...
08-11-2025 05:45:57 SddcMgmtDomain[4246]: [INFO] VCF Installer is not ready yet, sleeping for 30 seconds ...
08-11-2025 05:46:29 SddcMgmtDomain[4246]: [INFO] VCF Installer is not ready yet, sleeping for 30 seconds ...
08-11-2025 05:47:01 SddcMgmtDomain[4246]: [INFO] VCF Installer is not ready yet, sleeping for 30 seconds ...
08-11-2025 05:47:33 SddcMgmtDomain[4246]: [INFO] VCF Installer is not ready yet, sleeping for 30 seconds ...
08-11-2025 05:48:05 SddcMgmtDomain[4246]: [INFO] VCF Installer is not ready yet, sleeping for 30 seconds ...

Reproduction steps

...

Expected behavior

Installation will go further

Additional context

[dhruv-tyagi-broadcom]

Can you ping VCF Installer from Holorouter?

[miskaste]

Yes, I can.

root@holorouter [ ~ ]# ping 10.1.10.250
PING 10.1.10.250 (10.1.10.250) 56(84) bytes of data.
64 bytes from 10.1.10.250: icmp_seq=1 ttl=64 time=0.534 ms
64 bytes from 10.1.10.250: icmp_seq=2 ttl=64 time=0.511 ms
64 bytes from 10.1.10.250: icmp_seq=3 ttl=64 time=0.371 ms
64 bytes from 10.1.10.250: icmp_seq=4 ttl=64 time=0.489 ms
^C
--- 10.1.10.250 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3052ms
rtt min/avg/max/mdev = 0.371/0.476/0.534/0.062 ms
root@holorouter [ ~ ]#

[dhruv-tyagi-broadcom]

Great. This log message (VCF Installer is not ready yet, sleeping for 30 seconds) is shown when Holorouter is trying to hit the VCF Installer API to check if the API is available and continues till it responds properly. Let's try hitting the API manually from Holorouter and see if it responds. Run the following commands in your Holorouter in pwsh with config loaded (Running $config should show you the config loaded):

$Version = "9.0.1.0"
$site = "a"

 $siteCode = "Site-${site}"
$vcf_installer = $config."holodeck-sddc".$siteCode."vcf-installer"
$password = $vcf_installer.localUserPassword
$vcf_installer_hostname =  $vcf_installer.ip0

$vcf_installer_auth_body = @{
    username = "admin@local"
    password = $password
} | ConvertTo-Json -Depth 100

$request = Invoke-RestMethod -Uri "https://${vcf_installer_hostname}/v1/tokens" -Method "POST" -Body $vcf_installer_auth_body -ContentType 'application/json' -SkipCertificateCheck

$request

See if VCF Installer is responding to the request

[miskaste]

Thank you!

Response to request:

accessToken: eyJhbGciOiJIUzI1........................

It seems that the API call did not like the proxy server. The problem was solved by setting "no_proxy". Now the installation went further.