vmware / vmware/Holodeck

[Bug]: Portgroup not accessible from this host

Open
#138 9 comments 0 reactions 1 assignee View on GitHub

@jpurohit92 is already working on this.

Since Jun 22, 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

vCenter Cluster

Describe the bug

Holodeck and VCF version are both 9.1 - drop downs of the bug mask do not allow this to be selected

PortGroup is NSX based as per documentation.

New-HoloDeckConfig -Description "VCF 9.1" -TargetHost [vcenter] -Username administrator@vsphere.local -Password [password]
New-HoloDeckInstance -CIDR 10.3.0.0/20 -vSANMode ESA -Version 9.1.0.0 -DeployVcfAutomation -InstanceID vcf91 -DepotType Online

This runs fine for a while and fails with error:

18-06-2026 12:38:24 ESXBuild[6954]: [ERROR] Site Deployment failed.
18-06-2026 12:38:24 ESXBuild[6954]: [ERROR] 6/18/2026 12:38:24 PM New-VM Portgroup not accessible from this host.
18-06-2026 12:38:24 ESXBuild[6954]: [ERROR] HoloDeck deployment failed. Complete error diagnostics saved to: /holodeck-runtime/logs/holodeck-runtime-errors-site-a_18Jun2026_12_29.log
Exception: Failed to deploy HoloDeck

The cluster selected as an install target has four nodes; all of them are prepared with NSX and can access the NSX trunc portgroup. A holodeck instance with version 9.0.1 runs fine.

Reproduction steps
  1. New-HoloDeckConfig -Description "VCF 9.1" -TargetHost [vcenter] -Username administrator@vsphere.local -Password [password]
  2. New-HoloDeckInstance -CIDR 10.3.0.0/20 -vSANMode ESA -Version 9.1.0.0 -DeployVcfAutomation -InstanceID vcf91 -DepotType Online
Expected behavior

Create ESXi Host VMs without error

Relevant logs
=== FULL ERROR DIAGNOSTICS (DEPLOYMENT FAILED) ===
Timestamp: 18-06-2026 12:38:24
Total Errors in $Error Variable: 14
Current Function: ESXBuild


--- Error [0] (Most Recent) ---
Message: Exiting Function New-HoloSite
Exception Type: System.Management.Automation.RuntimeException
Script: /root/.local/share/powershell/Modules/HoloDeck/Modules/HoloSite.psm1
Line: 346
Stack Trace:
at New-HoloSite<Process>, /root/.local/share/powershell/Modules/HoloDeck/Modules/HoloSite.psm1: line 346
at New-HoloDeckInstance<Process>, /root/.local/share/powershell/Modules/HoloDeck/HoloDeck.psm1: line 1176
at <ScriptBlock>, <No file>: line 1


--- Error [1]  ---
Message: 6/18/2026 12:38:24 PM  New-VM          Portgroup not accessible from this host.
Exception Type: VMware.VimAutomation.Sdk.Types.V1.ErrorHandling.VimException.ViError
Script: /root/.local/share/powershell/Modules/HoloDeck/Modules/ESXiBuild.psm1
Line: 358
Stack Trace:
at New-HoloDeckESXi<Process>, /root/.local/share/powershell/Modules/HoloDeck/Modules/ESXiBuild.psm1: line 358
at New-HoloDeckESXiNodes<Process>, /root/.local/share/powershell/Modules/HoloDeck/Modules/ESXiBuild.psm1: line 615
at New-HoloSite<Process>, /root/.local/share/powershell/Modules/HoloDeck/Modules/HoloSite.psm1: line 181
at New-HoloDeckInstance<Process>, /root/.local/share/powershell/Modules/HoloDeck/HoloDeck.psm1: line 1176
at <ScriptBlock>, <No file>: line 1


--- Error [2]  ---
Message: Failed to deploy HoloDeck
Exception Type: System.Management.Automation.RuntimeException
Script: /root/.local/share/powershell/Modules/HoloDeck/HoloDeck.psm1
Line: 1208
Stack Trace:
at New-HoloDeckInstance<Process>, /root/.local/share/powershell/Modules/HoloDeck/HoloDeck.psm1: line 1208
at <ScriptBlock>, <No file>: line 1


--- Error [3]  ---
Message: Exiting Function New-HoloSite
Exception Type: System.Management.Automation.RuntimeException
Script: /root/.local/share/powershell/Modules/HoloDeck/Modules/HoloSite.psm1
Line: 346
Stack Trace:
at New-HoloSite<Process>, /root/.local/share/powershell/Modules/HoloDeck/Modules/HoloSite.psm1: line 346
at New-HoloDeckInstance<Process>, /root/.local/share/powershell/Modules/HoloDeck/HoloDeck.psm1: line 1176
at <ScriptBlock>, <No file>: line 1
Additional context

No response

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.