Share via

ASDK deployment fails at step 60.125 - how to fix it?

Jan-Hendrik Peters 1 Reputation point
2021-09-13T05:21:56.463+00:00

The Azure Stack SDK deployment repeatedly fails at step 60.125.125 with the error 

Invoke-EceAction : Type 'InvokeCLM' of Role 'CLM' raised an exception:
Exception calling "InstallApplications" with "0" argument(s): "One or more errors occurred.
  [1] UpgradeFailureException: [DeploymentProvider] [ServiceFabric] Application upgrade failure: fabric:/DeploymentProvider health is in Error state, hence aborting application Upgrade.
"
Detailed logs can be found at \\AzS-ERCS01\c$\MasLogs\CLM_Invoke-ContainerLifecycleManager_*.txt.
at Invoke-ContainerLifecycleManager, C:\CloudDeployment\Roles\CLM\ContainerLifecycleManager.psm1: line 108
at InvokeCLM, C:\CloudDeployment\Classes\CLM\CLM.psm1: line 20
at <ScriptBlock>, <No file>: line 60
at <ScriptBlock>, <No file>: line 58
At C:\CloudDeployment\Setup\Common\DeploySingleNodeCommon.ps1:924 char:5
+     Invoke-EceAction -RolePath $masterRole -ActionType $ActionPlan @d ...
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Exception calli...eManager_*.txt.:String) [Invoke-EceAction], InterfaceInvocationFailedException
    + FullyQualifiedErrorId : Exception calling "InstallApplications" with "0" argument(s): "One or more errors occurred.
  [1] UpgradeFailureException: [DeploymentProvider] [ServiceFabric] Application upgrade failure: fabric:/DeploymentProvider health is in Error state, hence aborting application Upgrade.
"
Detailed logs can be found at \\AzS-ERCS01\c$\MasLogs\CLM_Invoke-ContainerLifecycleManager_*.txt.,CloudEngine.Cmdlets.InvokeCmdlet

While the logs are very detailed, they don't point to the reason for the error.

Version: <Version>1.2102.0.9</Version>
Hardware: Standard E48s_v3, 4 SSD data disks 1TB each
Networking: Static IP

Small edit: Log uploaded: https://jhpworkshops.blob.core.windows.net/sonstige/CLM_Invoke-ContainerLifecycleManager_20210911-194217.log?sp=r&st=2021-09-13T07:49:56Z&se=2023-08-31T15:49:56Z&spr=https&sv=2020-08-04&sr=b&sig=HK2j2kkPH%2B9HpOI%2B2Iy5SDsrz%2BW7rWEdPwp59q7jdfY%3D

Azure Stack Hub
Azure Stack Hub
An extension of Azure for running apps in an on-premises environment and delivering Azure services in a datacenter.
180 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. TravisCragg-MSFT 5,681 Reputation points Microsoft Employee
    2021-09-16T00:21:45.643+00:00

    Although it is possible to get this working on an Azure VM, nested virtualization is not supported for the ASDK, so this is not a supported scenario.

    You can try a -rerun to see if you can continue the deployment. This error is due to several roles that have failed, so this will likely require a reinstall if you want to continue.

    I would look into others who have gotten this working on Azure and try to follow what they do. There are some specific things you have to change and configure in order to get this working.

    0 comments