locked
ASDK Deployment Failure - Step 60.120.121 RRS feed

  • Question

  • Ran into an error pretty far into the ASDK deployment on a bare-metal box.

    It looks like its passing my tenant FQDN instead of my tenant type "AzureCloud" in the 'Environment' parameter. Poked around the ps1 a bit but couldn't dig anything else up.

    Any suggestions?

    VERBOSE: 1> [IdentityProvider:Deployment] New-ActiveDirectoryApplication : BEGIN on ASDK01 as
    AZURESTACK\azurestackadmin - 3/26/2018 3:04:45 PM
    VERBOSE: 1> [IdentityProvider:Deployment] [IdentityProvider]: AzureAD Identity Provider Selected (AzureAD). - 3/26/2018
     3:04:45 PM
    VERBOSE: 1> [IdentityProvider:Deployment] Initialize-AADActiveDirectoryApplication : BEGIN on ASDK01 as
    AZURESTACK\azurestackadmin - 3/26/2018 3:04:45 PM

    Invoke-EceAction : 1> Cannot validate argument on parameter 'Environment'. The argument "<domain>.onmicrosoft.com"
    does not belong to the set "AzureCloud,AzureChinaCloud,AzureUSGovernment,AzureGermanCloud" specified by the
    ValidateSet attribute. Supply an argument that is in the set and then try the command again. - 3/26/2018 3:04:45 PM
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:675 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : ParameterArgumentValidationError,Initialize-AADActiveDirectoryApplication,CloudEngine.Cm
       dlets.InvokeCmdlet

    Invoke-EceAction : 1> Task: Invocation of interface 'Deployment' of role 'Cloud\Fabric\IdentityProvider' failed:
    Type 'Deployment' of Role 'IdentityProvider' raised an exception:
    Cannot validate argument on parameter 'Environment'. The argument "<domain>.onmicrosoft.com" does not belong to
    the set "AzureCloud,AzureChinaCloud,AzureUSGovernment,AzureGermanCloud" specified by the ValidateSet attribute. Supply
    an argument that is in the set and then try the command again.
     - 3/26/2018 3:04:45 PM
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:675 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    VERBOSE: Action: Action plan 'Deployment-Phase2-ConfigureStack' failed. - 3/26/2018 3:04:45 PM
    Invoke-EceAction : Action: Invocation of step 60.120 failed. Stopping invocation of action plan. - 3/26/2018 3:04:45 PM
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:675 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet



    • Edited by Medx Monday, March 26, 2018 8:37 PM
    Monday, March 26, 2018 8:28 PM

Answers

  • Hello,

    Can you run the following network diagnostics and paste the output in your reply.

      

    ### Check NetNat IPs 

    New-PSSession -ComputerName AzS-BGPNAT01

    Enter-PSSession –ComputerName AzS-BGPNAT01

    Get-NetIPConfiguration

    Get-NetNatExternalAddress

    Exit-PSSession

    <# Compare the IPv4Address entry on the external adapter (Hint: Not adapter with the 192.168.200.1 address)

    from Get-NetIPConfiguration to the IPAddress entry from Get-NetNatExternalAddress.  They will now be different. #>

     

     

    #Check for Qlogic Card

    function CheckQLogicDriver {

        write-host -ForegroundColor yellow "["(date -format "HH:mm:ss")"]" "Checking for Qlogic Adapter..."

        $IsQLogic = ($IsQLogic =  Get-NetAdapter)

        If ($IsQLogic)

            {

            If (($IsQLogic.InterfaceDescription -like "*QLogic*"))

                {

                write-host -ForegroundColor red "["(date -format "HH:mm:ss")"]" " -- WARNING : Qlogic Adapter Present. `

                - Contact your Server OEM to get the latest Qlogic driver software before deploying ASDK"

                $Global:ChecksFailure++

                }

                else

                {

                write-host -ForegroundColor green "["(date -format "HH:mm:ss")"]" " -- Not Present."

                $Global:ChecksSuccess++

                }

            }

            else

            {

            write-host -ForegroundColor green "["(date -format "HH:mm:ss")"]" " -- Not Present."

            $Global:ChecksSuccess++

            }

    }

    CheckQLogicDriver

     

    ### Runs Network Tests on VMs & Host

    Start-Transcript

    $AzSVM = Get-VM

    Invoke-command -Computername $AzSVM.name -ScriptBlock {TNC login.windows.net -port 443}

    Invoke-command -Computername $AzSVM.name -ScriptBlock {Ipconfig /all}

    Invoke-command -Computername $AzSVM.name -ScriptBlock {ipconfig /displaydns}

    ipconfig /all

    ipconfig /displaydns

    Stop-Transcript

     

    Let us know how it goes.

        

    We apologize for any inconvenience and appreciate your time and interest in Azure Stack.

    If you experience any issues with Azure Stack or the current ASDK release, please feel free to contact us.

                 

     Thanks


    Gary Gallanes

    Tuesday, March 27, 2018 11:10 PM

All replies

  • You may try redeploying using the -rerun parameter and see if that helps.

    NOTE: Make sure you are running the deployment as under the

    AzureStack\AzureStackAdmin account.

     

    cd C:\CloudDeployment\setup

    .\InstallAzureStackPOC.ps1 -rerun

     

    Just to confirm, is ASDK01 your Azure Stack host (bare-metal box)? If feasible you may reboot and then re-run.

     

    Refer the document Tutorial: redeploy the ASDK for more details on this topic.

     

    Also, do provide the following information:

     

    Build/Version:  

    Get-Content "C:\CloudDeployment\Configuration\Version\version.xml"

      

    Hardware: 

    How many CPU Cores, RAM, Get-Disk output

     

    Network: 

    Static or DHCP.

     

    The method used to access the Internet:

    NAT, Web Proxy, Transparent  Proxy, DMZ or Closed

    ---------------------------------------------------------------------------------------------------

    Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.

    Tuesday, March 27, 2018 6:39 AM
  • Thanks for the response Ajay.

    This is a bare metal install on a box with 16 cores and 96 GB on Server 2016 Datacenter.

    Current Network setup is Static.

    PS C:\CloudDeployment\setup> Get-Content "C:\CloudDeployment\Configuration\Version\version.xml"
    <Version>1.0.180302.1</Version>

    I did just notice as well looking for the Internet access that it appears the box no longer has internet access after running the deployment so I may have missed a step somewhere. Not sure if this is applicable to the error I'm getting.

    I've attempted a reboot of the bare metal box and a -rerun of the deployment and still encounter the same error.

    Tuesday, March 27, 2018 4:16 PM
  • Hello,

    Can you run the following network diagnostics and paste the output in your reply.

      

    ### Check NetNat IPs 

    New-PSSession -ComputerName AzS-BGPNAT01

    Enter-PSSession –ComputerName AzS-BGPNAT01

    Get-NetIPConfiguration

    Get-NetNatExternalAddress

    Exit-PSSession

    <# Compare the IPv4Address entry on the external adapter (Hint: Not adapter with the 192.168.200.1 address)

    from Get-NetIPConfiguration to the IPAddress entry from Get-NetNatExternalAddress.  They will now be different. #>

     

     

    #Check for Qlogic Card

    function CheckQLogicDriver {

        write-host -ForegroundColor yellow "["(date -format "HH:mm:ss")"]" "Checking for Qlogic Adapter..."

        $IsQLogic = ($IsQLogic =  Get-NetAdapter)

        If ($IsQLogic)

            {

            If (($IsQLogic.InterfaceDescription -like "*QLogic*"))

                {

                write-host -ForegroundColor red "["(date -format "HH:mm:ss")"]" " -- WARNING : Qlogic Adapter Present. `

                - Contact your Server OEM to get the latest Qlogic driver software before deploying ASDK"

                $Global:ChecksFailure++

                }

                else

                {

                write-host -ForegroundColor green "["(date -format "HH:mm:ss")"]" " -- Not Present."

                $Global:ChecksSuccess++

                }

            }

            else

            {

            write-host -ForegroundColor green "["(date -format "HH:mm:ss")"]" " -- Not Present."

            $Global:ChecksSuccess++

            }

    }

    CheckQLogicDriver

     

    ### Runs Network Tests on VMs & Host

    Start-Transcript

    $AzSVM = Get-VM

    Invoke-command -Computername $AzSVM.name -ScriptBlock {TNC login.windows.net -port 443}

    Invoke-command -Computername $AzSVM.name -ScriptBlock {Ipconfig /all}

    Invoke-command -Computername $AzSVM.name -ScriptBlock {ipconfig /displaydns}

    ipconfig /all

    ipconfig /displaydns

    Stop-Transcript

     

    Let us know how it goes.

        

    We apologize for any inconvenience and appreciate your time and interest in Azure Stack.

    If you experience any issues with Azure Stack or the current ASDK release, please feel free to contact us.

                 

     Thanks


    Gary Gallanes

    Tuesday, March 27, 2018 11:10 PM