locked
Azure Stack Installation on a Nested VM RRS feed

  • Question

  • In our Lab, I am doing a POC for Azure Stack. I am getting the below error during setup when it try to authenticate to Azure AD. I had configured a IP which had a nat ip for the host and the nat vm. But the installation is failing in the beginning. I am able to telnet to login.windows.net and graph.windows.net from the host machine. Do we require to configure any other ports in the firewall for the installation to succeed

    Verbose: InstallAzureStackPOC.ps1 -NATIPv4Subnet 192.168.20.0/24 -NATIPv4Address 192.168.20.15 -NATIPv4DefaultGateway 192.168.20.1 -EnvironmentDNS 192.168.20.10 -Verbose True -AdminPassword System.Security.SecureString

    Verbose: Starting AzureStack POC configuration.
    Verbose: Validating input parameters.
    Verbose: The host NIC is using a static IP.
    Verbose: Updating the host NIC DNS entries to provided DNS entries: '192.168.20.10' which will be used as DNS forwarders.
    Verbose: Syncing to the following time server: 'time.windows.com'.
    Verbose: Using provided static IP '192.168.20.15' for NAT.
    Error:
    Invoke-RestMethod : Unable to connect to the remote server
    At C:\CloudDeployment\Common\AzureADConfiguration.psm1:139 char:24
    + ... sResponse = Invoke-RestMethod -Method Get -Uri "$($AzureURIs.ARMUri)t ...
    +                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebException
        + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand

    Thanks,

    Manoj Koshy

    Friday, February 17, 2017 10:09 AM

Answers

  • This kind of scenario is not yet supported however you can find different blogs about a nested hypervisor setup. You also need to enable mac spoofing for Hyper-V or VMware ESXi before your VMs on you VM can travel outside through NAT.  Read my blog for VMware or this blog about Hyper-V.

    I wont recommend to install Azure Stack in a nested hypervisor setup yet, its unstable and does not provide you a good representation of Azure Stack. However, there is a chance that it is more stable with the latest Windows updates or with the latest ESX 6.5 version.

    Back to the error, first be sure you've got internet connectivity on your VM, thats something what you have to configure yourself, we cannot help you with that. If Internet access is working then there is something up with your DNS or firewall. The error indicates that the installation script could not connect with 'https://management.azure.com/tenants?api-version=2016-02-01'.

    Try this, it should give you an authentication failed.

    Invoke-RestMethod -Method Get -Uri https://management.azure.com/tenants?api-version=2016-02-01


    Cheers,

    Ruud
    Twitter:    Blog: AzureStack.Blog  LinkedIn:    
    Note: Please “Vote As Helpful” if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.


    Friday, February 17, 2017 12:59 PM

All replies

  • Hi,did you enable mac address spoofing one the VM ? otherwise it wont work

    Friday, February 17, 2017 10:40 AM
  • This kind of scenario is not yet supported however you can find different blogs about a nested hypervisor setup. You also need to enable mac spoofing for Hyper-V or VMware ESXi before your VMs on you VM can travel outside through NAT.  Read my blog for VMware or this blog about Hyper-V.

    I wont recommend to install Azure Stack in a nested hypervisor setup yet, its unstable and does not provide you a good representation of Azure Stack. However, there is a chance that it is more stable with the latest Windows updates or with the latest ESX 6.5 version.

    Back to the error, first be sure you've got internet connectivity on your VM, thats something what you have to configure yourself, we cannot help you with that. If Internet access is working then there is something up with your DNS or firewall. The error indicates that the installation script could not connect with 'https://management.azure.com/tenants?api-version=2016-02-01'.

    Try this, it should give you an authentication failed.

    Invoke-RestMethod -Method Get -Uri https://management.azure.com/tenants?api-version=2016-02-01


    Cheers,

    Ruud
    Twitter:    Blog: AzureStack.Blog  LinkedIn:    
    Note: Please “Vote As Helpful” if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.


    Friday, February 17, 2017 12:59 PM
  • Thanks for the reply.

    I enables mac address spoofing on the nested vm. I made some progress on the installation after i enabled internet access for both host and nat vm without proxy. But it is failing after running for more than three hours with the below error.

    2017-02-21 15:57:53 Verbose  1> 1> Step: Status of step '(FBI) Create Storage Accounts' is 'Success'.
    2017-02-21 15:57:53 Verbose  1> 1> Step: Running step 144 - (FBI) Register Usage for SRP
    2017-02-21 15:57:53 Verbose  1> 1> Task: Running interface 'Migrate' of role 'Cloud\Fabric\FabricRingServices\SRP'.
    2017-02-21 15:57:53 Verbose  1> 1> Interface: Path to module: C:\CloudDeployment\Roles\XRP\XRP.psd1
    2017-02-21 15:57:53 Verbose  1> 1> Interface: Running interface Migrate (Roles\XRP\XRP.psd1, RegisterUsageAndCreateDefaultRPQuota)
    2017-02-21 15:57:57 Warning  1> 1> The names of some imported commands from the module 'XRP' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
    2017-02-21 15:57:58 Verbose  1> 1> Registering Usage for RPs
    2017-02-21 15:57:58 Verbose  1> 1> Registering Usage for RP: Microsoft.Storage
    2017-02-21 15:58:31 Verbose  1> 1> Registered Usage for RP: Microsoft.Storage
    2017-02-21 15:58:32 Verbose  1> 1> Creating default quota for Microsoft.Storage.Admin from MAS-Xrp01.AzureStack.Local...
    2017-02-21 15:58:55 Verbose  1> 1> Created default quota for Microsoft.Storage.Admin from MAS-Xrp01.AzureStack.Local...
    2017-02-21 15:58:55 Verbose  1> 1> Interface: Interface Migrate completed.
    2017-02-21 15:58:55 Verbose  1> 1> Task: Task completed.
    2017-02-21 15:58:55 Verbose  1> 1> Step: Status of step '(FBI) Register Usage for SRP' is 'Success'.
    2017-02-21 15:58:55 Verbose  1> 1> Action: Action plan 'Deployment-Phase5-CreateStorageAccounts' completed.
    2017-02-21 15:58:55 Verbose  1> 1> Action: Status of 'Deployment-Phase5-CreateStorageAccounts' is 'Success'.
    2017-02-21 15:58:55 Verbose  1> 1> Task: Status of action 'Deployment-Phase5-CreateStorageAccounts' of role 'Cloud' is 'Success'.
    2017-02-21 15:58:55 Verbose  1> Step: Status of step 'Phase 5 - DeployServices' is 'Error'.
    2017-02-21 15:58:55 Error    1> Action: Invocation of step 60.140 failed. Stopping invocation of action plan.
    2017-02-21 15:58:55 Verbose  1> Action: Status of 'Deployment-Phase2-ConfigureStack' is 'Error'.
    2017-02-21 15:58:55 Verbose  1> Task: Status of action 'Deployment-Phase2-ConfigureStack' of role 'Cloud' is 'Error'.
    2017-02-21 15:58:55 Verbose  Step: Status of step 'Phase 2 - ConfigureVMs' is 'Error'.
    2017-02-21 15:58:55 Error    Action: Invocation of step 60 failed. Stopping invocation of action plan.

    Wednesday, February 22, 2017 10:44 AM
  • Please rerun the deployment.

    cd C:\CloudDeployment\Configuration
    .\InstallAzureStackPOC.ps1 -rerun

    Also check if you can can resolve external DNS domains and have Internet connectivity on the MAS-BGPNAT01 and MAS-WAS01. Then make sure the timezones and time is correct on all the servers. Run the script below to correct and rerun the deployment again.

    # Syncs MAS-DC01 with external time server time.windows.com
    Invoke-Command -Computer  MAS-DC01 -ScriptBlock { w32tm /config /manualpeerlist:time.windows.com /syncfromflags:manual /reliable:yes /update;w32tm /resync /force}
    
    # Resync all VMs with MAS-DC01
    $ALLVMS = @("MAS-ACS01","MAS-ADFS01","MAS-ASql01","MAS-BGPNAT01","MAS-CA01","MAS-Con01","MAS-DC01","MAS-Gwy01","MAS-NC01", "MAS-SLB01", "MAS-SUS01", "MAS-WAS01", "MAS-Xrp01")
    Invoke-Command -Computer $ALLVMS -ScriptBlock { w32tm /config /update /syncfromflags:DOMHIER }


    Cheers,

    Ruud
    Twitter:    Blog: AzureStack.Blog  LinkedIn:    
    Note: Please “Vote As Helpful” if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

    Wednesday, February 22, 2017 6:30 PM
  • Thanks for the reply.

    Now the installation failed at 60.120. Please find the attached logs

    2017-02-23 05:46:45 Verbose  1> 1> Step: Status of step '(FBI) Controller Configuration' is 'Success'.
    2017-02-23 05:46:45 Verbose  1> 1> Action: Action plan 'Deployment-Phase4-DeploySRPControllerServices' completed.
    2017-02-23 05:46:45 Verbose  1> 1> Action: Status of 'Deployment-Phase4-DeploySRPControllerServices' is 'Success'.
    2017-02-23 05:46:45 Verbose  1> 1> Task: Status of action 'Deployment-Phase4-DeploySRPControllerServices' of role 'Cloud' is 'Success'.
    2017-02-23 05:48:54 Verbose  1> 3> ConfigureAdfs : END on MASPOC as AZURESTACK\AzureStackAdmin
    2017-02-23 05:48:54 Verbose  1> 3> Interface: Interface Configure completed.
    2017-02-23 05:48:54 Verbose  1> 3> Task: Task completed.
    2017-02-23 05:48:54 Verbose  1> 3> Step: Status of step '(Katal) Configure ADFS' is 'Success'.
    2017-02-23 05:48:54 Verbose  1> 3> Action: Action plan 'Deployment-Phase4-DeployADFS' completed.
    2017-02-23 05:48:54 Verbose  1> 3> Action: Status of 'Deployment-Phase4-DeployADFS' is 'Success'.
    2017-02-23 05:48:54 Verbose  1> 3> Task: Status of action 'Deployment-Phase4-DeployADFS' of role 'Cloud' is 'Success'.
    2017-02-23 05:48:54 Verbose  1> Step: Status of step 'Phase 4 - ConfigureVMs-Part2' is 'Error'.
    2017-02-23 05:48:54 Error    1> Action: Invocation of step 60.120 failed. Stopping invocation of action plan.
    2017-02-23 05:48:54 Verbose  1> Action: Status of 'Deployment-Phase2-ConfigureStack' is 'Error'.
    2017-02-23 05:48:54 Verbose  1> Task: Status of action 'Deployment-Phase2-ConfigureStack' of role 'Cloud' is 'Error'.
    2017-02-23 05:48:54 Verbose  Step: Status of step 'Phase 2 - ConfigureVMs' is 'Error'.
    2017-02-23 05:48:54 Error    Action: Invocation of step 60 failed. Stopping invocation of action plan.

    Friday, February 24, 2017 6:01 AM
  • Try to rerun the deployment again or reboot the host and rerun again. If that fails then run my script to see if there are any issues.

    ## Change this two variables
    $AadUser = "admin@company.onmicrosoft.com"
    $Password = 'password'
    
    $NETVMS = @("MAS-BGPNAT01","MAS-DC01","MAS-WAS01")
    $AadTenantid = ($AadUser -split '@')[1]
    $Credential = New-Object System.Management.Automation.PSCredential(($AadUser) , `
    (ConvertTo-SecureString -String $Password  -AsPlainText -Force))
    
    ### Runs Network Tests to login.windows.net on 443 from "MAS-DC01","MAS-WAS01,MAS-BGPNAT01"
    $ConTests = $NETVMS | % {
        Invoke-command -ComputerName $_ -ScriptBlock {
            write-output '--------------------------------------------------------------------------------'
            write-output "`n`n`t`t`t$env:computername (Timezone,DNS config,DNS lookup,Webrequest)`n" 
            (Get-TimeZone).displayname
            Get-NetIPConfiguration | ft IPv4Address,@{n='dns';e={$_.dnsserver.serveraddresses}}
            Resolve-DnsName -Name bing.com -Server 192.168.200.6 | select -First 1 | ft name,ipaddress,type,name
            Invoke-WebRequest https://login.windows.net/common/.well-known/openid-configuration -UseBasicParsing | ft statuscode,content
        }
    
    }
    
    ### Opens a Session on MAS-WAS01 and Authenticate to login.windows.net and get an Azure Stack Token. 
    $TokenTest = invoke-command -Computername MAS-WAS01 -ArgumentList $AadTenantid ,$Credential -ScriptBlock {
    
        ### Downloads and Imports the AzureRM module 1.2.6 installed #######
        Set-PSRepository -Name "PSGallery" -InstallationPolicy Trusted
        $AzureModule = "c:\Program Files\WindowsPowerShell\Modules\AzureRM\1.2.6\AzureRM.psd1"
        if (Test-Path $AzureModule){
            Import-Module $AzureModule -Global -WarningAction SilentlyContinue
              } else { 
                    Install-Module -Name AzureRM -RequiredVersion 1.2.6 -AllowClobber 
                    }
        Import-Module -Name "AzureRM" -Erroraction SilentlyContinue -WarningAction SilentlyContinue
        write-output '--------------------------------------------------------------------------------'
        write-output "`t`t`t$env:computername (Get-AzureStackToken)`n"
        $AadTenantid ,$Credential = $args[0],$args[1]
        $AuthorityEndpoint = "https://login.windows.net"
        $armEndpoint = "https://api.azurestack.local”
        $response = Invoke-RestMethod "${armEndpoint}/metadata/endpoints?api-version=1.0"
        $armResourceId = $response.authentication.audiences[0]
        $token = Get-AzureStackToken -Authority $AuthorityEndpoint -AadTenantId $AadTenantid  -Resource $armResourceId -Credential $Credential -Verbose 
        if (!$token){write-warning 'Couldnt retrieve token'}else{$token}
    }
    
    
    ### Tests time sync between MAS-WAS01, MAS-BGPNAT01 and MAS-DC01
    $TimeTest =write-output "`n`n`t`t`t$env:computername (Net Time Test)`n`n";$TimeTest += (net time \\MAS-DC01)[0]; $TimeTest+="`n" + (net time \\MAS-WAS01)[0];$TimeTest+= "`n" + (net time \\MAS-BGPNAT01)[0]
    
    ### Retrieves and test DNS forwarders on MAS-DC01
    $DNSTest=@();$DNSTest += write-output "`n`t`t`t$env:computername (DNS forwarder test)`n"
    $DNSforwarder = Get-DnsServerForwarder -ComputerName 192.168.200.6
    if ($DNSforwarder.ipaddress){
    $DNSTest += ($DNSforwarder.ipaddress | where IsIPv6SiteLocal -eq $false).ipaddresstostring | % {write-output "`n`t`t`t$_" ;(Resolve-DnsName bing.com -Server $_ |  select -First 1 | ft name,ipaddress,type,name) }
    } else { write-output "No DNS forwarders found." }
    
    
    $DNSTest;$TimeTest;$ConTests;$TokenTest


    Cheers,

    Ruud
    Twitter:    Blog: AzureStack.Blog  LinkedIn:    
    Note: Please “Vote As Helpful” if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

    Friday, February 24, 2017 9:33 AM
  • Hi Ruud,

    Thanks for the reply.

    In my POC environment, MAS-BGNAT01 and Azure Stack host has internet connection using a Nated IP as per Microsoft article. Do we require internet connection on MAS-DC01 and MAS-WAS01?.  Both MAS-DC01 and MAS-WAS01 is installed with their own address space and only my machines in the nated subnet has access to the internet.

    Regards,

    Manoj Koshy

    Monday, February 27, 2017 5:07 AM
  • Hi Manoj, you should have internet access on the MAS-WAS01 and MAS-DC01, its routed through NAT via MAS-BGPNAT01. 

    Cheers,

    Ruud
    Twitter:    Blog: AzureStack.Blog  LinkedIn:    
    Note: Please “Vote As Helpful” if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

    Monday, February 27, 2017 3:26 PM
  • Azure Stack TP3 has been released on March 1, 2017.

    If you are experiencing any issues with the TP2 release, please download and redeploy using the latest Azure Stack POC deployment package

    Please see the updated deployment documentation:

    https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-run-powershell-script

    And updated Azure Stack Docs:

    https://docs.microsoft.com/en-us/azure/azure-stack/

    If you experience any issues with TP3 release, feel free to contact us.

    https://azure.microsoft.com/en-us/blog/hybrid-application-innovation-with-azure-and-azure-stack/

    Wednesday, March 1, 2017 7:05 PM
  • I try  to configure Azure Stack TP3 in our lab with Azure AD and -ADFS options in our Lab. It failed after running for 4 hours with the below errors.

     

    Error with Azure AD option

     

    2017-03-03 17:31:00 Verbose  1> 1> Querying shares for storage service

    2017-03-03 17:31:13 Verbose  1> 1> Available shares include ClusterStorage$ SU1_Infrastructure_1 SU1_ManagementLibrary_1 SU1_TenantLibrary_1 SU1_Tenant_1 SU1_VmTemp_1

    2017-03-03 17:31:14 Verbose  1> 1> Get the storage account key for ACS

    2017-03-03 17:31:34 Verbose  1> 1> Configuring Storage Service storage account information

    2017-03-03 17:31:34 Verbose  1> 1> Start to configure the storage account.

    2017-03-03 17:31:38 Verbose  1> 1> Start to configure the storage account srphealthaccount.

    2017-03-03 17:31:38 Verbose  1> 1> Start to set the storage account name into settings by service.

    2017-03-03 17:31:39 Verbose  1> 1> Start to set the storage account key into settings by service.

    2017-03-03 17:31:39 Verbose  1> 1> Set the storage account successfully.

    2017-03-03 17:31:39 Verbose  1> 1> Invoke-IACSPostConfigure is done.

    2017-03-03 17:31:39 Verbose  1> 1> Interface: Interface Configure completed.

    2017-03-03 17:31:39 Verbose  1> 1> Task: Task completed.

    2017-03-03 17:31:39 Verbose  1> 1> Step: Status of step '60.140.147 - (ACS) Configure Storage Accounts information' is 'Success'.

    2017-03-03 17:31:39 Verbose  1> 1> Action: Action plan 'Deployment-Phase5-ConfigureWASAndCreateStorageAccounts' completed.

    2017-03-03 17:31:39 Verbose  1> 1> Action: Status of 'Deployment-Phase5-ConfigureWASAndCreateStorageAccounts' is 'Success'.

    2017-03-03 17:31:39 Verbose  1> 1> Task: Status of action 'Deployment-Phase5-ConfigureWASAndCreateStorageAccounts' of role 'Cloud' is 'Success'.

    2017-03-03 17:31:39 Verbose  1> Step: Status of step '60.140 - Phase 5 - DeployServices' is 'Error'.

    2017-03-03 17:31:39 Error    1> Action: Invocation of step 60.140 failed. Stopping invocation of action plan.

    2017-03-03 17:31:39 Verbose  1> Action: Status of 'Deployment-Phase2-ConfigureStack' is 'Error'.

    2017-03-03 17:31:39 Verbose  1> Task: Status of action 'Deployment-Phase2-ConfigureStack' of role 'Cloud' is 'Error'.

    2017-03-03 17:31:39 Verbose  Step: Status of step '60 - Phase 2 - ConfigureVMs' is 'Error'.

    2017-03-03 17:31:39 Error    Action: Invocation of step 60 failed. Stopping invocation of action plan.

     

    Error with –ADFS Switch

     

     

    2017-03-07 01:58:46 Verbose  1> 2> Querying shares for storage service

    2017-03-07 01:59:04 Verbose  1> 2> Available shares include ClusterStorage$ SU1_Infrastructure_1 SU1_ManagementLibrary_1 SU1_TenantLibrary_1 SU1_Tenant_1 SU1_VmTemp_1

    2017-03-07 01:59:44 Verbose  1> 2> Interface: Interface Validate completed.

    2017-03-07 01:59:44 Verbose  1> 2> Task: Task completed.

    2017-03-07 01:59:44 Verbose  1> 2> Step: Status of step '60.61.83.13 - Validate Azure-consistent Storage.' is 'Success'.

    2017-03-07 01:59:44 Verbose  1> 2> Action: Action plan 'Deployment' completed.

    2017-03-07 01:59:44 Verbose  1> 2> Action: Status of 'Deployment' is 'Success'.

    2017-03-07 01:59:44 Verbose  1> 2> Task: Status of action 'Deployment' of role 'Cloud\Fabric\ACS' is 'Success'.

    2017-03-07 01:59:44 Verbose  1> 2> Step: Status of step '60.61.83 - (ACS) Setup Azure-consistent Storage.' is 'Success'.

    2017-03-07 01:59:44 Verbose  1> 2> Action: Action plan 'Deployment-Phase3-ACSDeployment' completed.

    2017-03-07 01:59:44 Verbose  1> 2> Action: Status of 'Deployment-Phase3-ACSDeployment' is 'Success'.

    2017-03-07 01:59:44 Verbose  1> 2> Task: Status of action 'Deployment-Phase3-ACSDeployment' of role 'Cloud' is 'Success'.

    2017-03-07 01:59:44 Verbose  1> Step: Status of step '60.61 - Phase 3 - ConfigureVMs-Part1' is 'Error'.

    2017-03-07 01:59:44 Error    1> Action: Invocation of step 60.61 failed. Stopping invocation of action plan.

    2017-03-07 01:59:44 Verbose  1> Action: Status of 'Deployment-Phase2-ConfigureStack' is 'Error'.

    2017-03-07 01:59:44 Verbose  1> Task: Status of action 'Deployment-Phase2-ConfigureStack' of role 'Cloud' is 'Error'.

    2017-03-07 01:59:44 Verbose  Step: Status of step '60 - Phase 2 - ConfigureVMs' is 'Error'.

    2017-03-07 01:59:44 Error    Action: Invocation of step 60 failed. Stopping invocation of action plan.

     Manoj Koshy

    Wednesday, March 8, 2017 8:38 AM
  • Hi Manoj,

    Could you share what are the variable you have change?

    Hence, did execute Invoke-AzureStackDepolymentPreCheck.ps1 with all success status. 

    Got the following errors when executing InstallAzureStackPOC -UseADFS

    at Trace-Error, C:\CloudDeployment\Common\Tracer.psm1: line 44
    at Start-Test, C:\CloudDeployment\Roles\Common\RoleHelpers.psm1: line 1244
    at Test-BareMetalRole, C:\CloudDeployment\Roles\PhysicalMachines\TestPhysicalMachines.psm1: line 86
    at Validate, C:\CloudDeployment\Classes\BareMetal\BareMetal.psm1: line 69
    at <ScriptBlock>, <No file>: line 9 - 3/26/2017 12:49:08 PM
    Invoke-EceAction : Task: Invocation of interface 'Validate' of role 'Cloud\Infrastructure\BareMetal' failed:
    Function 'BareMetal:Validate' in module 'Classes\BareMetal\BareMetal.psm1' raised an exception:
    One or more validation test failed for Role 'BareMetal' on machine 'AZURESTACKTP3'
    For detailed test results look at file
    '\\AZURESTACKTP3\C$\CloudDeployment\Logs\Tests\TestResults_AZURESTACKTP3_BareMetal_2017-03-26-12-48-51.xml'
    Test Failed: Validate that at least 12 cores are available in computer .
    Command            Arguments
    L

    o

    c

    a

    t

    i

    o

    n
    -------            ---------
    -
    Start-Test         {Parameters=CloudEngine.Configurations.EceInterfaceParameters, Script=System.Collections.Hashtable}
    R
    Test-BareMetalRole {Parameters=CloudEngine.Configurations.EceInterfaceParameters, ErrorAction=Stop, Verbose=True}
    T
                       {}
    B
    <ScriptBlock>      {C:\CloudDeployment\CloudDeployment.psd1, CloudEngine.Configurations.EceInterfaceParameters}
    <
    at Trace-Error, C:\CloudDeployment\Common\Tracer.psm1: line 44
    at Start-Test, C:\CloudDeployment\Roles\Common\RoleHelpers.psm1: line 1244
    at Test-BareMetalRole, C:\CloudDeployment\Roles\PhysicalMachines\TestPhysicalMachines.psm1: line 86
    at Validate, C:\CloudDeployment\Classes\BareMetal\BareMetal.psm1: line 69
    at <ScriptBlock>, <No file>: line 9 - 3/26/2017 12:49:08 PM
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:526 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OperationStopped: (One or more val...        <
    :String) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : One or more validation test failed for Role 'BareMetal' on machine 'AZURESTACKTP3'
        For detailed test results look at file '\\AZURESTACKTP3\C$\CloudDeployment\Logs\Tests\TestResults_AZURESTACKTP3_Ba
       reMetal_2017-03-26-12-48-51.xml'
    Test Failed: Validate that at least 12 cores are available in computer .
        Command            Arguments
            L

            o

            c

            a

            t

            i

            o

            n
        -------            ---------
            -
        Start-Test         {Parameters=CloudEngine.Configurations.EceInterfaceParameters, Script=System.Collections.Hashta
       ble} R
        Test-BareMetalRole {Parameters=CloudEngine.Configurations.EceInterfaceParameters, ErrorAction=Stop, Verbose=True}
            T
                           {}
            B
        <ScriptBlock>      {C:\CloudDeployment\CloudDeployment.psd1, CloudEngine.Configurations.EceInterfaceParameters}
            <
    ,CloudEngine.Cmdlets.InvokeCmdlet

    VERBOSE: Step: Status of step '0.12 - (DEP) Validate Physical Machines' is 'Error'. - 3/26/2017 12:49:08 PM
    Invoke-EceAction : Action: Invocation of step 0.12 failed. Stopping invocation of action plan. - 3/26/2017 12:49:08 PM
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:526 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    VERBOSE: Action: Status of 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' is 'Error'. - 3/26/2017 12:49:08 PM
    COMPLETE: Task Cloud - Deployment-Phase0-DeployBareMetalAndBGPAndNAT
    VERBOSE: Task: Status of action 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' of role 'Cloud' is 'Error'. - 3/26/2017
     12:49:08 PM
    VERBOSE: Step: Status of step '0 - Phase 0 - Configure physical machine and external networking' is 'Error'. -
    3/26/2017 12:49:08 PM
    Invoke-EceAction : Action: Invocation of step 0 failed. Stopping invocation of action plan. - 3/26/2017 12:49:08 PM
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:526 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    Please advice.  Many thanks.


    Kelvin Teang

    Monday, March 27, 2017 4:22 AM