locked
Azure Stack TP2 deployment fails at 60.160.178 RRS feed

  • Question

  • The installation was originally started with the -AADDirectoryTenantName as shown below, but the error says that it's looking for an object in a different tenant "kodakalaris.com" which appears to be the root of the failure, any idea how I can get past this? I've already attempted the -rerun 4 times.

    .\InstallAzureStackPOC.ps1 -AADDirectoryTenantName IMCustest.onmicrosoft.com

     - 12/15/2016 10:57:01 AM
    VERBOSE: 1> 7> Set up Powershell Azure environment - 12/15/2016 10:57:01 AM
    VERBOSE: 1> 7> Loading module from path 'D:\KeyVault\Tools\Helpers.psm1'. - 12/15/2016 10:57:01 AM
    VERBOSE: 1> 7> Exporting function 'Get-LocalizedString'. - 12/15/2016 10:57:01 AM
    VERBOSE: 1> 7> Exporting function 'Get-CertificateByThumbprintOrPfx'. - 12/15/2016 10:57:01 AM
    VERBOSE: 1> 7> Importing function 'Get-CertificateByThumbprintOrPfx'. - 12/15/2016 10:57:01 AM
    VERBOSE: 1> 7> Importing function 'Get-LocalizedString'. - 12/15/2016 10:57:01 AM
    VERBOSE: 1> 7> GET https://api.azurestack.local//metadata/endpoints?api-version=2015-01-01 with
    0-byte payload - 12/15/2016 10:57:01 AM
    VERBOSE: 1> 7> received 303-byte response of content type application/json; charset=utf-8 -
    12/15/2016 10:57:01 AM
    VERBOSE: 1> 7> Retrieved the following values from ARM endpoints API: - 12/15/2016 10:57:01 AM
    VERBOSE: 1> 7> Active Directory Endpoint: https://login.windows.net/ - 12/15/2016 10:57:01 AM
    VERBOSE: 1> 7> Active Directory Service Endpoint Resource ID:
    https://api.azurestack.local/bb3b11c0-d984-4176-9d54-fd43cb179d61 - 12/15/2016 10:57:01 AM
    VERBOSE: 1> 7> Removing any exisiting Azure RM environment named 'MyAzureStack'. - 12/15/2016
    10:57:01 AM
    VERBOSE: 1> 7> Initialize Azure Powershell environment with AAD and ARM. - 12/15/2016 10:57:01 AM
    VERBOSE: 1> 7> Login to the Azure RM account as service admin. - 12/15/2016 10:57:01 AM
    Invoke-EceAction : 1> 7> Task: Invocation of interface 'Deployment' of role
    'Cloud\Fabric\KeyVault' failed:
    Function 'Invoke-IKeyVaultInstall' in module 'Roles\KeyVault\KeyVault.psd1' raised an exception:
    AADSTS50001: The application named
    https://api.azurestack.local/bb3b11c0-d984-4176-9d54-fd43cb179d61 was not found in the tenant
    namedkodakalaris.com.  This can happen if the application has not been installed by the
    administrator of the tenant or consented to by any user in the tenant.  You might have sent your
    authentication request to the wrong tenant.
    Trace ID: c246ced4-7c91-480c-971f-cf8918aa5c62
    Correlation ID: 06999a1c-57d7-4347-bf7f-d42ced9e1f02
    Timestamp: 2016-12-15 18:57:00Z: The remote server returned an error: (400) Bad Request.
    at Initialize-KeyVaultAzureRmEnvironment, D:\KeyVault\Tools\InitializeAzureRmEnvironment.ps1:
    line 66
    at Execute-KeyVaultInstall, D:\KeyVault\Tools\KeyVault.psm1: line 76
    at <ScriptBlock>, <No file>: line 12 - 12/15/2016 10:57:01 AM
    At C:\CloudDeployment\Configuration\InstallAzureStackPOC.ps1:652 char:1
    + Invoke-EceAction -RolePath Cloud -ActionType Deployment @startHash -V ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : CloseError: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Microsoft.Azure.Commands.Profile.AddAzureRMAccountCommand,CloudEngi
       ne.Cmdlets.InvokeCmdlet

    VERBOSE: 1> 7> Step: Status of step '(KV) KeyVault Deployment' is 'Error'. - 12/15/2016 10:57:01
    AM
    Invoke-EceAction : 1> 7> Action: Invocation of step 60.160.178 failed. Stopping invocation of
    action plan. - 12/15/2016 10:57:01 AM
    At C:\CloudDeployment\Configuration\InstallAzureStackPOC.ps1:652 char:1
    + Invoke-EceAction -RolePath Cloud -ActionType Deployment @startHash -V ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    VERBOSE: 1> 7> Action: Status of 'Deployment-Phase6-KeyVault' is 'Error'. - 12/15/2016 10:57:01 AM
    COMPLETE: Task Cloud - Deployment-Phase6-KeyVault
    VERBOSE: 1> 7> Task: Status of action 'Deployment-Phase6-KeyVault' of role 'Cloud' is 'Error'. -
    12/15/2016 10:57:01 AM
    VERBOSE: 1> Step: Status of step 'Phase 6 - Install Resource Providers' is 'Error'. - 12/15/2016
    10:57:01 AM
    Invoke-EceAction : 1> Action: Invocation of step 60.160 failed. Stopping invocation of action
    plan. - 12/15/2016 10:57:01 AM
    At C:\CloudDeployment\Configuration\InstallAzureStackPOC.ps1:652 char:1
    + Invoke-EceAction -RolePath Cloud -ActionType Deployment @startHash -V ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    VERBOSE: 1> Action: Status of 'Deployment-Phase2-ConfigureStack' is 'Error'. - 12/15/2016 10:57:01
     AM
    COMPLETE: Task Cloud - Deployment-Phase2-ConfigureStack
    VERBOSE: 1> Task: Status of action 'Deployment-Phase2-ConfigureStack' of role 'Cloud' is 'Error'.
    - 12/15/2016 10:57:01 AM
    VERBOSE: 2> Interface: Interface Deployment completed. - 12/15/2016 10:57:02 AM
    COMPLETE: Task Cloud\Fabric\Console - Deployment
    VERBOSE: 2> Task: Task completed. - 12/15/2016 10:57:02 AM
    COMPLETE: Step 221 - (FBI) Setup Console VMs
    VERBOSE: 2> Step: Status of step '(FBI) Setup Console VMs' is 'Success'. - 12/15/2016 10:57:02 AM
    STARTING: Step 222 - (FBI) Setup Console VMs
    VERBOSE: 2> Step: Running step 222 - (FBI) Setup Console VMs - 12/15/2016 10:57:02 AM
    STARTING: Task Cloud\Fabric\Console - Configure
    VERBOSE: 2> Task: Running interface 'Configure' of role 'Cloud\Fabric\Console'. - 12/15/2016
    10:57:02 AM
    VERBOSE: 2> Interface: Path to module: C:\CloudDeployment\Roles\Console\Console.psd1 - 12/15/2016
    10:57:02 AM
    VERBOSE: 2> Interface: Running interface Configure (Roles\Console\Console.psd1, ConfigureConsole)
    - 12/15/2016 10:57:02 AM
    WARNING: 2> The names of some imported commands from the module 'Console' 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. - 12/15/2016 10:57:05 AM
    VERBOSE: 2> Moving Content to \\MAS-Con01\C$ - 12/15/2016 10:57:07 AM
    VERBOSE: 2> Interface: Interface Configure completed. - 12/15/2016 10:57:09 AM
    COMPLETE: Task Cloud\Fabric\Console - Configure
    VERBOSE: 2> Task: Task completed. - 12/15/2016 10:57:09 AM
    COMPLETE: Step 222 - (FBI) Setup Console VMs
    VERBOSE: 2> Step: Status of step '(FBI) Setup Console VMs' is 'Success'. - 12/15/2016 10:57:09 AM
    VERBOSE: 2> Action: Action plan 'Deployment-Phase2-DeployConsoleVMs' completed. - 12/15/2016
    10:57:09 AM
    COMPLETE: Action 'Deployment-Phase2-DeployConsoleVMs'
    VERBOSE: 2> Action: Status of 'Deployment-Phase2-DeployConsoleVMs' is 'Success'. - 12/15/2016
    10:57:09 AM
    COMPLETE: Task Cloud - Deployment-Phase2-DeployConsoleVMs
    VERBOSE: 2> Task: Status of action 'Deployment-Phase2-DeployConsoleVMs' of role 'Cloud' is
    'Success'. - 12/15/2016 10:57:09 AM
    VERBOSE: Step: Status of step 'Phase 2 - ConfigureVMs' is 'Error'. - 12/15/2016 10:57:09 AM
    Invoke-EceAction : Action: Invocation of step 60 failed. Stopping invocation of action plan. -
    12/15/2016 10:57:09 AM
    At C:\CloudDeployment\Configuration\InstallAzureStackPOC.ps1:652 char:1
    + Invoke-EceAction -RolePath Cloud -ActionType Deployment @startHash -V ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    ~Alvin

    Thursday, December 15, 2016 7:21 PM

Answers

  • This is a bug in the Azure Stack deployment, it takes the AzureAD domain of the authenticated user instead of the provided 'AADDirectoryTenantName' one. Applications are created in the right tenant, only the keyvault installation part function 'Invoke-IKeyVaultInstall' targets the wrong directory. It is passed down to the function by the deployment engine.

    For now, the AzureAD user you provide must belong to the same directory you specify in the AADDirectoryTenantName parameter. 


    Cheers,

    Ruud
    Twitter:    Blog: www.ruudborst.nl  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.



    Tuesday, December 20, 2016 1:04 PM

All replies

  • Hi,

    Can you please let us know what username you entered when running deployment?

    Also, the full command you executed when running deployment?

    Thanks

    Daniel.

    Thursday, December 15, 2016 7:38 PM
  • Full command was "

    .\InstallAzureStackPOC.ps1 -AADDirectoryTenantName IMCustest.onmicrosoft.com

    username was my corporate identity (I don't want to put it here) which has access to multiple tenants, I'm planning to reset and try again with an identity that is only in the intended target tenant.

    ~Alvin

    Friday, December 16, 2016 3:24 PM
  • Hi,

    Thanks for the update.

    Please let us know if the retry is successful.

    Thanks

    Daniel.

    Friday, December 16, 2016 7:50 PM
  • This is a bug in the Azure Stack deployment, it takes the AzureAD domain of the authenticated user instead of the provided 'AADDirectoryTenantName' one. Applications are created in the right tenant, only the keyvault installation part function 'Invoke-IKeyVaultInstall' targets the wrong directory. It is passed down to the function by the deployment engine.

    For now, the AzureAD user you provide must belong to the same directory you specify in the AADDirectoryTenantName parameter. 


    Cheers,

    Ruud
    Twitter:    Blog: www.ruudborst.nl  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.



    Tuesday, December 20, 2016 1:04 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 6:46 PM