Closed VDI-Tech-Guy closed 4 months ago
Here is what my WLD File looks like, i have changed the FQDN in the file for my domain
This issue was reported by @lamw - https://github.com/vmware/powershell-module-for-vmware-cloud-foundation/issues/266
To Resolve have to edit the file "PowerVCF.psm1" located depending on linux/mac/windows in different locations
Windows - "C:\Users\admin\Documents\PowerShell\Modules\PowerVCF\2.4.1.1000\PowerVCF.psm1"
and change the Write-Error on line 1951 to a Write-Output.
Also something else worth noting, if you use the UNLICENSED Version of 5.1.1 when building the Managment Cluster with SDDC and manager, you have to go into the SDDC Manager and put in the licenses before running workload domain with licenses as it will need to be installed into the SDDC Manager prior to executing correctly
For Workload Domain you must have licensing for it to work correctly cannot get past it.
Another thing to note if nothing in the log indicates the problem after you do the fix above and still get an error but it doesnt output enough information you can run the command manually to figure out the issue
New-VCFWorkloadDomain -json .\wld-w01.json -Verbose
In my cases it was licensing information as per my previous comment about licenses not imported b/c the main deployment didnt have licenses
In the original PS1 to deploy out the enviornment, it said there was a 60 day trial license, however in the code for the WLD it more indicates that it might require the licensing for 5.1.1
With my file setup with No Licensing im seeing the following error.
Is this because there is no License keys installed in the WLD powershell script? The code will import the 4 Hosts then halt after that
I also noticed in 5.1.1 when trying to create a WLD manually it was asking about importing image bundles for NSX and ESXi before i could progress further (from that it required Authentication to Broadcoms Portal to access your entitlements). Have you found this to be the case?