locked
Deployment stuck @ Invocation of step 60.120.121 failed. Stopping invocation of action plan. RRS feed

  • Question

  • Hi All , 

    The deployment is stuck @ Invocation of step 60.120.121 failed. Stopping invocation of action plan.

    Below is the log :- 

    2018-04-12 10:46:56 Verbose  1> [IdentityProvider:Deployment] ERROR: An error occurred while trying to verify connection to the graph endpoint 'https://login.windows.net/87dbc464-d60e-489f-8a41-xxxxxxxxx/.well-known/openid-configuration': The remote name could not be resolved: 'login.windows.net'

    Additional details: 
    2018-04-12 10:46:56 Warning  1> Task: Invocation of interface 'Deployment' of role 'Cloud\Fabric\IdentityProvider' failed: 

    Type 'Deployment' of Role 'IdentityProvider' raised an exception:



    An error occurred while trying to verify connection to the graph endpoint 'https://login.windows.net/87dbc464-d60e-489f-8a41-xxxxxxxxx/.well-known/openid-configuration': The remote name could not be resolved: 'login.windows.net'

    Additional details: 
    at Assert-GraphConnection, C:\CloudDeployment\Roles\IdentityProvider\GraphAPI.psm1: line 361
    at Get-GraphToken, C:\CloudDeployment\Roles\IdentityProvider\GraphAPI.psm1: line 406
    at Update-GraphAccessToken, C:\CloudDeployment\Roles\IdentityProvider\GraphAPI.psm1: line 552
    at Initialize-GraphEnvironment, C:\CloudDeployment\Roles\IdentityProvider\GraphAPI.psm1: line 289
    at Initialize-AADActiveDirectoryApplication, C:\CloudDeployment\Roles\IdentityProvider\IdentityProvider.psm1: line 90
    at New-ActiveDirectoryApplication, C:\CloudDeployment\Roles\IdentityProvider\IdentityProvider.psm1: line 41
    at Deployment, C:\CloudDeployment\Classes\IdentityProvider\IdentityProvider.psm1: line 18
    at <ScriptBlock>, <No file>: line 39
    at <ScriptBlock>, <No file>: line 37
    2018-04-12 10:46:56 Warning  1> Task: Retrying interface 'Deployment' of role 'Cloud\Fabric\IdentityProvider'...
    2018-04-12 10:46:56 Verbose  1> Task: Running interface 'Deployment' of role 'Cloud\Fabric\IdentityProvider'. Attempt #2. totalRetries = 2 (Retry 1 of 2.)
    2018-04-12 10:46:56 Verbose  1> Wait for 60 seconds before attempting retry.
    2018-04-12 10:46:57 Verbose  2> 2> [IBC:Configure] Finish configure IBC.
    2018-04-12 10:46:57 Verbose  2> 2> Interface: Interface Configure completed.
    2018-04-12 10:46:57 Verbose  2> 2> Task: Task completed.
    2018-04-12 10:47:56 Verbose  1> Interface: Path to module: C:\CloudDeployment\Classes\IdentityProvider\IdentityProvider.psm1
    2018-04-12 10:47:56 Verbose  1> Interface: Running interface Deployment (Classes\IdentityProvider\IdentityProvider.psm1, IdentityProvider:Deployment)
    2018-04-12 10:47:57 Warning  1> [IdentityProvider:Deployment] The names of some imported commands from the module 'RoleHelpers' 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.
    2018-04-12 10:47:57 Warning  1> [IdentityProvider:Deployment] The names of some imported commands from the module 'IdentityProvider' 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.
    2018-04-12 10:47:58 Warning  1> [IdentityProvider:Deployment] The names of some imported commands from the module 'RoleHelpers' 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.
    2018-04-12 10:47:58 Warning  1> [IdentityProvider:Deployment] The names of some imported commands from the module 'IdentityProvider' 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.
    2018-04-12 10:47:58 Verbose  1> [IdentityProvider:Deployment] New-ActiveDirectoryApplication : BEGIN on AGILECOESTACK as AZURESTACK\AzureStackAdmin
    2018-04-12 10:47:58 Verbose  1> [IdentityProvider:Deployment] [IdentityProvider]: AzureAD Identity Provider Selected (AzureAD).
    2018-04-12 10:47:58 Verbose  1> [IdentityProvider:Deployment] Initialize-AADActiveDirectoryApplication : BEGIN on AGILECOESTACK as AZURESTACK\AzureStackAdmin
    2018-04-12 10:47:58 Verbose  1> [IdentityProvider:Deployment] Initializing the module to use Graph environment 'AzureCloud' (with refresh token) in directory tenant '87dbc464-d60e-489f-8a41-xxxxxxxxx'.
    2018-04-12 10:47:58 Verbose  1> [IdentityProvider:Deployment] Graph Environment initialized: client-request-id: f77c95de-df28-4a1a-9e71-9c77d39139c7
    2018-04-12 10:47:58 Verbose  1> [IdentityProvider:Deployment] Testing connection to graph environment using endpoint 'https://login.windows.net/87dbc464-d60e-489f-8a41-xxxxxxxxx/.well-known/openid-configuration'
    2018-04-12 10:47:58 Verbose  1> [IdentityProvider:Deployment] GET https://login.windows.net/87dbc464-d60e-489f-8a41-xxxxxxxxx/.well-known/openid-configuration with 0-byte payload
    2018-04-12 10:48:09 Verbose  1> [IdentityProvider:Deployment] ERROR: An error occurred while trying to verify connection to the graph endpoint 'https://login.windows.net/87dbc464-d60e-489f-8a41-xxxxxxxxx/.well-known/openid-configuration': The remote name could not be resolved: 'login.windows.net'

    _____________________________________________________________________________________________________

    Build/Version:1.0.180329.1


    Directory type:Azure AD


    Hardware:CPU Cores- 16 Cores , RAM - 192 GB, 

     Number Friendly Name Serial Number                    HealthStatus         OperationalStatus      Total Size Partition
                                                                                                                 Style
    ------ ------------- -------------                    ------------         -----------------      ---------- ----------
    1      INTEL SSDS... PHDV734300VT1P2DGN               Healthy              Online                    1.09 TB GPT
    0      INTEL SSDS... PHDW73010392240E                 Healthy              Online                  223.57 GB GPT
    5      Msft Virtu...                                  Healthy              Online                     120 GB MBR
    6      SU1_Volume    {f7c47cdd-0fe0-4e37-970f-8898... Healthy              Online                    2.94 TB GPT


    Network:Static 


    The method used to access the Internet:Direct Proxy

    BareMetal or Nested Hyper-V:BareMetal


    Deployment parameters used: We are executing the script in the AzureStack\AzureStackAdmin account 
       Yes we have re-run the script using the script cd C:\CloudDeployment\setup
       .\InstallAzureStackPOC.ps1 -rerun


    Thursday, April 12, 2018 6:27 AM

Answers

  • Ahh, fixed it, so I realized from a few google searches that it's related to networking, specifically with being able to access https://login.windows.net/f7a480f6-6833-4b64-b1fd-xxxxxxx/.well-known/openid-configuration and receiving a json file.

    I was able to access this fine on my workstation, but for some reason on the ASDK host computer it was being blocked by a DNS filter on our firewall. When that was resolved I was able to access the URL fine and resumed the setup via:

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

    DG


    Thursday, April 12, 2018 11:45 PM

All replies

  • Hi All , 

    I was able to get past the error 

    Thank you 

    Regards 

    Nirmal Johnson

    Thursday, April 12, 2018 8:00 AM
  • Glad to know you got it working. Thanks for the update. You could share the steps that you took to remedy this issue for benefitting the other community members.

    If you have any specific questions around this issue do let us know.

    Thursday, April 12, 2018 9:14 AM
  • Hi All , 

    I was able to get past the error 

    Thank you 

    Regards 

    Nirmal Johnson

    What did you do to fix this? I'm stick at the exact same spot... 

    DG

    Thursday, April 12, 2018 11:09 PM
  • Ahh, fixed it, so I realized from a few google searches that it's related to networking, specifically with being able to access https://login.windows.net/f7a480f6-6833-4b64-b1fd-xxxxxxx/.well-known/openid-configuration and receiving a json file.

    I was able to access this fine on my workstation, but for some reason on the ASDK host computer it was being blocked by a DNS filter on our firewall. When that was resolved I was able to access the URL fine and resumed the setup via:

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

    DG


    Thursday, April 12, 2018 11:45 PM
  • Ahh, fixed it, so I realized from a few google searches that it's related to networking, specifically with being able to access https://login.windows.net/f7a480f6-6833-4b64-b1fd-xxxxxxx/.well-known/openid-configuration and receiving a json file.

    I was able to access this fine on my workstation, but for some reason on the ASDK host computer it was being blocked by a DNS filter on our firewall. When that was resolved I was able to access the URL fine and resumed the setup via:

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

    DG


    Thanks for the update and for sharing the solution that helped rectify the issue.

    Friday, April 13, 2018 6:09 AM