vmware / vmware/Holodeck

[Bug]: Can't deploy 9.1 using DeveloperMode and online Depottype

Open
#175 1 comment 0 reactions 1 assignee View on GitHub

@dhruv-tyagi-broadcom is already working on this.

Since Sep 18, 2026.

bug
Dominant language
HTML
Stars
30
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Holorouter Version

9.1

VCF Version

VCF 9.1

Target Type

Standalone ESX Host

Describe the bug

When trying to deploy v9.1 using -DeveloperMode, there is no proper way to have the Service ID/ Activation code for the Software Depot.

Reproduction steps

Do a new deployment for 9.1 with -DeveloperMode

Expected behavior

To install correctly.

Relevant logs

Additional context

Workarround/Fix:

This does go against the unattended setup of DeveloperMode, (using a offline depot might make more sense for a unattended setup..)

Holodeck.psm1:

-424    $Global:BroadcomBuildToken = ConvertTo-SecureString -AsPlainText -Force -String $env:brcm_build_token
+424	# For VCF 9.1+, skip token request here - it will be done after VCF Installer deployment
+425    if($Version_site_a -like "9.1*"){
+426	Write-Log -Message "VCF 9.1+ detected. Online depot token will be requested after VCF Installer deployment." -Level "INFO"
+427	}
+428	else{
+429	# For VCF 9.0 and earlier, keep existing behavior

-610    $Global:BroadcomBuildToken = ConvertTo-SecureString -AsPlainText -Force -String $env:brcm_build_token
+610	# For VCF 9.1+, skip token request here - it will be done after VCF Installer deployment
+611    if($Version_site_a -like "9.1*"){
+612	Write-Log -Message "VCF 9.1+ detected. Online depot token will be requested after VCF Installer deployment." -Level "INFO"
+613	}
+614	else{
+615	# For VCF 9.0 and earlier, keep existing behavior

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.