New-SDNExpressiDNSConfiguration in SDN Express Module doesn't work
wiconlon opened this issue · 2 comments
New-SDNExpressiDNSConfiguration takes RestName as a parameter, which is the URI of the resource server without https:// at the beginning, it then creates a new variable called $uri which adds the https:// internally and uses that for most functions, however when calling New-NetworkControllerIDNSServerConfiguration it passes RestName rather than uri, which throws an error.
I tried fixing this on my own machine to see if that fix alone would correct the problem, the script gets farther but ends up failing at New-NetworkControllerIDNSServerConfiguration after hanging for a long period of time:
PSMessageDetails :
Exception : System.InvalidOperationException: Terminating error was thrown while executing 'C:\Windows\system32\WindowsPowerShell\v1.0\Modules\NetworkController\Microsoft.NetworkController.Powershell.dll' operation on the server side endpoint
'https://nc-stamp70.cfdev.nttest.microsoft.com/networking/V1/operations/050c65da-c570-42b9-bc7e-c3e29169e231'. ---> System.Management.Automation.CmdletInvocationException: An error occured.
--- End of inner exception stack trace ---
at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)
TargetObject : https://nc-stamp70.cfdev.nttest.microsoft.com/networking/V1/operations/050c65da-c570-42b9-bc7e-c3e29169e231
CategoryInfo : InvalidOperation: (https://nc-stam...7e-c3e29169e231:Uri) [New-NetworkCont...erConfiguration], InvalidOperationException
FullyQualifiedErrorId : ODataEndpointProxyInvokeFailure,New-NetworkControllerIDnsServerConfiguration
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at New-NetworkControllerIDnsServerConfiguration, : line 209
at New-SDNExpressiDNSConfiguration, C:\E2EWorkload\SDNExpress\scripts2\SDNExpressModule.psm1: line 749
at , : line 1
PipelineIterationInfo : {}
having similar problem with
New-NetworkControllerCredential, which throws error:
New-NetworkControllerCredential : Terminating error was thrown while executing
'C:\Windows\system32\WindowsPowerShell\v1.0\Modules\NetworkController\Microsoft.NetworkController.Powershell.dll' operation on the server side endpoint
'https://nc.7srv.local/networking/v1/credentials/1'.
At line:1 char:1
- New-NetworkControllerCredential -ConnectionUri "https://nc.7srv.local ...
-
+ CategoryInfo : InvalidOperation: (https://nc.7srv...1/credentials/1:String) [New-NetworkControllerCredential], InvalidOperationException + FullyQualifiedErrorId : ODataEndpointProxyInvokeFailure,New-NetworkControllerCredential
Any resolution to these issues? I'm also running into the same error when running 'Get-NetworkControllerCredential'.
The command executes 'ok' when running it locally on the Network Controller, but not remotely. I'm using SDNExpress to deploy. All runs fine until the script gets stuck in a infinite loop while checking if the Network Controller is responding. Digging into the script I see that it's attempting to run 'Get-NetworkControllerCredential'. Running the command manually with the appropriate -ConnectionUri parameter results in the same error referenced above in juffus' post.
Again, the command works ok when run on one of the Network Controller VMs, so it would seem like perhaps a security issue. However, by default these scripts appear to set Network Controller ClientAuthentication to 'none'. Any suggestions are welcomed.
Thanks.