Closed jonathan-vella closed 3 years ago
Hi - thanks for raising this - I've seen this issue recently too, and we're investigating. The hope is that we can fix soon.
I am seeing similar issues now where I am unable to provision the virtual switches: It just spins on the networks that I was not provisioning switches on. I've tried a few ways now, and I think this is a WAC issue
+1 on this issue for me too. Are there any workarounds currently?
Got a bit further. The CredSSP message popped up and when I clicked 'Yes' I got this failure on the 6 NICs
I fixed this by setting the locale to en-us but now I'm back to the original problem. Its trying to create vSwitchs for 10 minutes the day errors out. There is certainly bugs in the Cluster creation wizard.
@mattmcspirit did we ever get to the bottom of this?
with last "Cluster Creation" extension update it worked smoothly for me :)
can confirm that the new cluster creation extension fixed it for me too
Great - thanks. I can also confirm that updating to the very latest Cluster Creation extension fixes the deployment issues, so please update accordingly. I'll update steps to reflect the need to have an updated extension.
hey folks, seems like i have hit a brick wall. i cannot get past the "define networks" section. behavior is very erratic; sometime i get lucky and the following error is displayed:
"We couldn’t configure network adapters. Please try again. Error: Connecting to remote server 11.0.0.6 failed with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM..." --> to eliminate this i have created a gpo which will allow some traffic
In some other cases, WAC itself crashes. When this happens WAC displays thh following "Error Couldn't get user info. Source Go to source. Type Error Message ajax error
And in some others, some NICs do get configured. What is common is that CPU usage across all HCI nodes goes up to 25%. Any hints or ideas? thanks.