locked
TP3 Deployment Fails RRS feed

  • Question

  • I've attempted deploying TP3 3 times from scratch, additional times with -rerun switch, consistently getting the error below, at which point the deployment process halts. Hardware is Cisco UCS C220 and was successfully running TP2.

    Invoke-EceAction : 1> Action: Invocation of step 60.61 failed. Stopping invocation of action
    plan. - 3/19/2017 11:43:35 AM
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:526 char:5
    +    Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    Any suggestions are appreciated. Thanks

    Monday, March 20, 2017 12:38 PM

Answers

All replies

  • Hi Eric,,

    Can you please confirm that the host machine has a D drive?  Typically if you are booting from VHD the VHD becomes the C drive and the underlying drive hosting the VHD becomes D.  The join path error is trying to create a path from where it is executing, not the target.  If the host machine does not have a D drive or that is assigned to an CD/DVD with nothing inserted then this may be causing the issue.  You can try changing drive assignments on the host such that there is a volume mounted to D.  Note that the full path does not have to be there, it is constructing the path and PowerShell simply needs a volume mounted on D.  This is something that will be addressed in later releases.

    If this does not apply, then please try to Redeploy Azure Stack TP3 using the following command:

     

    Import-ModuleC:\CloudDeployment\CloudDeployment.psd1 -Force

    Import-ModuleC:\CloudDeployment\ECEngine\EnterpriseCloudEngine.psd1 -Force

    Invoke-EceAction-RolePath Cloud -ActionType Deployment -Start 60 -Verbose

     

    Also - Azure Stack requires access to the Internet either directly or through a transparent proxy.

    Public IP's are not required by Azure Stack TP3. 2 private NAT IP addresses assigned via DHCP or statically are all that is required.

    Both the host IP and the new IP assigned to the MAS-BGPNAT01 (by DHCP or static IP) must be able to access Internet. Ports 80 and 443 are used under the graph.windows.net and login.windows.net domains.

    -      Azure Stack TP3 does not support Web Proxy for Internet access.

    -      Make sure to disable ALL but one network adapter.

    If your environment DOESN'T have DHCP enabled

    You must include the following parameters to you deploy command to assign an IP to the MAS-BGPNAT gateway:

    .\InstallAzureStackPOC.ps1 -AdminPassword $adminpass -AADAdminCredential $aadcred

    -NatIPv4Subnet 10.10.10.0/24 -NatIPv4Address 10.10.10.3 -NatIPv4DefaultGateway 10.10.10.1

    If DNS resolution seems to be the issue:

    -          Use the optional -EnvironmentDNS setup parameter to add an external DNS server. 

    A DNS server is created as part of the Azure Stack deployment. To allow computers inside the solution to resolve names outside of the stamp, provide your existing infrastructure DNS server or a reliable known public DNS Server IP. The in-stamp DNS server forwards unknown name resolution requests to this server.

    Once network settings have been verified:

    -          Redeploy with the command below:

    Import-ModuleC:\CloudDeployment\CloudDeployment.psd1 -Force

    Import-ModuleC:\CloudDeployment\ECEngine\EnterpriseCloudEngine.psd1 -Force

    Invoke-EceAction-RolePath Cloud -ActionType Deployment -Start 60 -Verbose

    NOTE: Make sure you are running the deployment as under the AzureStack\AzureStackAdmin account.

    If you continue to receive error at step 60.61:

    -          Reboot the Host and MAS-Gwy01 VM.

    -          Make sure all VM roles are up by checking the roles in 'Failover Cluster Manager'

    -          Redeploy

     

    Let us know how it goes,

    TP3 Azure Stack Docs:

    https://docs.microsoft.com/en-us/azure/azure-stack/

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

    https://azure.microsoft.com/en-us/blog/hybrid-application-innovation-with-azure-and-azure-stack/

    If you continue experience any issues with TP3 release, feel free to contact us.

    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

    Thanks,


    Gary Gallanes

    Tuesday, March 21, 2017 3:48 PM
  • When I boot from the VHD or mount it in the host OS, it also creates a second disk. During the bcdboot process, the mounting the vhd takes the next 2 available drive letters, and the script assigns E: to the host's physical drive. When I boot into the cloudbuilder.vhd this second smaller disk takes the D: assignment. It is a small drive 346 MB. I can free up D: from here, but I can't reassign the physical drive from E: to D:.

    Is this normal? Nothing I've read references this additional drive being mounted.

    Wednesday, March 22, 2017 11:25 PM
  • Hi Eric,This is normal. My POC is configured they same way. Booted CloudBuilder.vhdx to C: at 120GB with a 346MB drive assigned to D: and my physical C: drive re-assigned to E:

    This could also be caused by a certificate issue too. Can you post more of the exception that is being thrown at step 60.61? 

    Thanks, 


    Gary Gallanes

    Friday, March 24, 2017 1:05 AM
  • Hello,

    Our investigation has determined this to be a known issue with TP3 that has been addressed in the TP3 refresh build released on April 6, 2017.

     

    Please download and redeploy using the latest Azure Stack TP3 Refresh POC deployment package

     

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

    If you continue experience any issues with TP3 refresh, feel free to contact us.

     

    TP3 refresh 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

      

     Thanks,


    Gary Gallanes

    Thursday, April 6, 2017 7:16 PM