Answered by:
Azure POC TP3 install fails

Question
-
Install fails at deployment of role Cloud\Fabric\VirtualMachines as shown below. Please advise.
Thanks, Paul
---------------------------------------------------------------------------------------
Invoke-EceAction : Task: Invocation of interface 'Deployment' of role 'Cloud\Fabric\VirtualMachines' failed:
Function 'VirtualMachines:Deployment' in module 'Classes\VirtualMachines\VirtualMachines.psm1' raised an exception:
The VM '192.168.200.224' didn't start in 900 seconds.
Command Arguments
------- ---------
Wait-VMPSConnection {VMNames=192.168.200.224, SetupAccountCredential=System.Management.Automation.PSCredential,
Timeo...
Add-GuestVMs {Parameters=CloudEngine.Configurations.EceInterfaceParameters, ErrorAction=Stop, Verbose=True}
{}
<ScriptBlock> {C:\CloudDeployment\CloudDeployment.psd1, CloudEngine.Configurations.EceInterfaceParameters}
at Trace-Error, C:\CloudDeployment\Common\Tracer.psm1: line 44
at Wait-VMPSConnection, C:\CloudDeployment\Roles\VirtualMachine\VirtualMachine.psm1: line 2137
at Add-GuestVMs, C:\CloudDeployment\Roles\VirtualMachine\VirtualMachine.psm1: line 457
at Deployment, C:\CloudDeployment\Classes\VirtualMachines\VirtualMachines.psm1: line 39
at <ScriptBlock>, <No file>: line 9 - 5/9/2017 5:16:55 PM
At C:\CloudDeployment\Setup\DeploySingleNode.ps1:535 char:5
+ Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (The VM '192.168...}
:String) [Invoke-EceAction], Exception
+ FullyQualifiedErrorId : The VM '192.168.200.224' didn't start in 900 seconds.
Command Arguments
------- ---------
Wait-VMPSConnection {VMNames=192.168.200.224, SetupAccountCredential=System.Management.Automation.PSCredential, T
meo...
Add-GuestVMs {Parameters=CloudEngine.Configurations.EceInterfaceParameters, ErrorAction=Stop, Verbose=True
{}
<ScriptBlock> {C:\CloudDeployment\CloudDeployment.psd1, CloudEngine.Configurations.EceInterfaceParameters}
,CloudEngine.Cmdlets.InvokeCmdlet
VERBOSE: Step: Status of step '0.14 - (DEP) Deploy AD Virtual Machine' is 'Error'. - 5/9/2017 5:16:55 PM
Invoke-EceAction : Action: Invocation of step 0.14 failed. Stopping invocation of action plan. - 5/9/2017 5:16:55 PM
At C:\CloudDeployment\Setup\DeploySingleNode.ps1:535 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'. - 5/9/2017 5:16:55 PM
COMPLETE: Task Cloud - Deployment-Phase0-DeployBareMetalAndBGPAndNAT
VERBOSE: Task: Status of action 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' of role 'Cloud' is 'Error'. - 5/9/201
5:16:55 PM
VERBOSE: Step: Status of step '0 - Phase 0 - Configure physical machine and external networking' is 'Error'. - 5/9/20
5:16:55 PM
Invoke-EceAction : Action: Invocation of step 0 failed. Stopping invocation of action plan. - 5/9/2017 5:16:55 PM
At C:\CloudDeployment\Setup\DeploySingleNode.ps1:535 char:5
+ Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Invoke-EceAction], Exception
+ FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet
PS C:\CloudDeployment\Setup>Wednesday, May 10, 2017 12:35 AM
Answers
-
Hi Paul,
The log from your deployment failure at step 0.14 (DEP) indicates MAS-DC01 could not start.
This typically occurs when the Deployment host does not meet the minimum requirements.
If you deployment Host has at least 96GB of memory and the deployment script has not been modified we can move forward with the next steps in troubleshooting.
Open up Failover Cluster manager and try to start the 'virtual machine' MAS-BGPNAT01' and rerun.
Please report the error if you got one.
An additional step would be to delete the Role an thus the VM from cluster manager and rerun the setup. It should re-create the VM again. If that doesnt work then try delete it again and this time remove the 'C:\ClusterStorage\Volume1\SHARES\SU1_INFRASTRUCTURE_1\MAS-BGPNAT01 directory. Now the vhdx will be recreated and reprovisioned with DSC.
Let us know how it goes.
We apologize for any inconvenience and appreciate your time and interest in Azure Stack.
If you continue 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/
TP3 Azure Stack Docs:
https://docs.microsoft.com/en-us/azure/azure-stack/
https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-troubleshooting
https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-diagnostics
https://aka.ms/GetAzureStackLogs
Gary Gallanes
- Proposed as answer by DanielSavage [MSFT] Wednesday, May 10, 2017 5:20 PM
- Marked as answer by Gary Gallanes [HCL Technologies] Wednesday, June 14, 2017 7:42 PM
Wednesday, May 10, 2017 3:23 PM