Holorouter Version
9.1
VCF Version
VCF 9.1
Target Type
vCenter Cluster
Describe the bug
Running Remove-HoloDeckInstance with Holodeck 9.1 and a custom -DNSDomain deletes the ESX VMs but not the VCF Installer VM.
The ESX VMs are named hd01-esx-01a, but the VCF Installer VM is named hd01-vcfinstaller-a.site-a.hd01.lab
In 9.0.2 I ran without passing DNSDomain and the VM was named hd01-vcfinstaller-a.
I haven't tried 9.0.2 with -DNSDomain, so this could be present in their too.
Reproduction steps
- Deploy a VCF 9.1 Holodeck instance with
-ManagementOnly -DNSDomain hd01.lab -Site "a"
- Wait for deployment to finish
- Destroy the instance with
Remove-HoloDeckInstance
Expected behavior
The ESX and VCF Installer VMs are deleted.
Relevant logs
Additional context
No response
Holorouter Version
9.1
VCF Version
VCF 9.1
Target Type
vCenter Cluster
Describe the bug
Running
Remove-HoloDeckInstancewith Holodeck 9.1 and a custom-DNSDomaindeletes the ESX VMs but not the VCF Installer VM.The ESX VMs are named
hd01-esx-01a, but the VCF Installer VM is namedhd01-vcfinstaller-a.site-a.hd01.labIn 9.0.2 I ran without passing DNSDomain and the VM was named
hd01-vcfinstaller-a.I haven't tried 9.0.2 with
-DNSDomain, so this could be present in their too.Reproduction steps
-ManagementOnly -DNSDomain hd01.lab -Site "a"Remove-HoloDeckInstanceExpected behavior
The ESX and VCF Installer VMs are deleted.
Relevant logs
Additional context
No response