locked
Azure stack dev kit installtion failure RRS feed

  • Question

  • Hello All,

    i am trying to install asdk on a physical server with powershell 5 installed. I get the below error. Please help. Quiet urgent.

    PS C:\> cd .\AzureStack_Installer

    PS C:\AzureStack_Installer> 
    PS C:\AzureStack_Installer> 
    PS C:\AzureStack_Installer> .\asdk-installer.ps1 
    At C:\AzureStack_Installer\asdk-installer.ps1:121 char:86
    + ... "Header header-logged-out  position-relative f4 py-3" role="banner" >
    +                                                                          ~
    Missing file specification after redirection operator.
    At C:\AzureStack_Installer\asdk-installer.ps1:136 char:21
    + </a>                </li>
    +                     ~
    The '<' operator is reserved for future use.
    At C:\AzureStack_Installer\asdk-installer.ps1:140 char:21
    + </a>                </li>
    +                     ~
    The '<' operator is reserved for future use.
    At C:\AzureStack_Installer\asdk-installer.ps1:145 char:21
    + </a>                </li>
    +                     ~
    The '<' operator is reserved for future use.
    At C:\AzureStack_Installer\asdk-installer.ps1:150 char:21
    + </a>                </li>
    +                     ~
    The '<' operator is reserved for future use.
    At C:\AzureStack_Installer\asdk-installer.ps1:154 char:21
    + </a>                </li>
    +                     ~
    The '<' operator is reserved for future use.
    At C:\AzureStack_Installer\asdk-installer.ps1:387 char:185
    + ... TF-8" method="post"><input name="utf8" type="hidden" value="&#x2713;" ...
    +                                                                 ~
    The ampersand (&) character is not allowed. The & operator is reserved for future use; wrap an ampersand in double 
    quotation marks ("&") to pass it as part of a string.
    At C:\AzureStack_Installer\asdk-installer.ps1:391 char:18
    + </form>          <h3 class="pt-2">Join GitHub today</h3>
    +                  ~
    The '<' operator is reserved for future use.
    At C:\AzureStack_Installer\asdk-installer.ps1:864 char:602
    + ... ureStack-Tools/commit/02301485f59a005c807e0c3991dbe0d5e098cb43">)</a>
    +                                                                      ~
    The '<' operator is reserved for future use.
    At C:\AzureStack_Installer\asdk-installer.ps1:870 char:53
    +   <summary class="btn-link" aria-haspopup="dialog" >
    +                                                     ~
    Missing file specification after redirection operator.
    Not all parse errors were reported.  Correct the reported errors and try again.
        + CategoryInfo          : ParserError: (:) [], ParseException
        + FullyQualifiedErrorId : MissingFileSpecification
     

    PS C:\AzureStack_Installer> 

    Tuesday, July 31, 2018 4:49 AM

All replies

  • It looks like you are referring to the steps outlined in this document Prepare the ASDK host computer and  Install the Azure Stack Development Kit (ASDK). Try invoking the script as show in the screenshot, ensure that there are no spaces in the cmdlet.

     


    Firstly, try invoking the cmdlet from an elevated PowerShell (Run as administrator):
    Set-ExecutionPolicy Unrestricted -force

    This command sets the user preference for the shell execution policy to RemoteSigned. Just as a note, ensure that you only invoke trusted scripts.

    Tuesday, July 31, 2018 11:00 AM
  • Still same error.

    Is there any other pre-requisite like loading azure rm power shell module? I think not required as we have not reached that stage, but I may be wrong.

     

    PS C:\Windows\System32> C:\AzureStack_Installer\asdk-installer.ps1
    At C:\AzureStack_Installer\asdk-installer.ps1:121 char:86
    + ... "Header header-logged-out  position-relative f4 py-3" role="banner" >
    +                                                                          ~
    Missing file specification after redirection operator.
    At C:\AzureStack_Installer\asdk-installer.ps1:136 char:21
    + </a>                </li>
    +                     ~
    The '<' operator is reserved for future use.
    At C:\AzureStack_Installer\asdk-installer.ps1:140 char:21
    + </a>                </li>
    +                     ~
    The '<' operator is reserved for future use.
    At C:\AzureStack_Installer\asdk-installer.ps1:145 char:21
    + </a>                </li>
    +                     ~
    The '<' operator is reserved for future use.
    At C:\AzureStack_Installer\asdk-installer.ps1:150 char:21
    + </a>                </li>
    +                     ~
    The '<' operator is reserved for future use.
    At C:\AzureStack_Installer\asdk-installer.ps1:154 char:21
    + </a>                </li>
    +                     ~
    The '<' operator is reserved for future use.
    At C:\AzureStack_Installer\asdk-installer.ps1:387 char:185
    + ... TF-8" method="post"><input name="utf8" type="hidden" value="&#x2713;" ...
    +                                                                 ~
    The ampersand (&) character is not allowed. The & operator is reserved for future use; wrap an 
    ampersand in double quotation marks ("&") to pass it as part of a string.
    At C:\AzureStack_Installer\asdk-installer.ps1:391 char:18
    + </form>          <h3 class="pt-2">Join GitHub today</h3>
    +                  ~
    The '<' operator is reserved for future use.
    At C:\AzureStack_Installer\asdk-installer.ps1:864 char:602
    + ... ureStack-Tools/commit/02301485f59a005c807e0c3991dbe0d5e098cb43">)</a>
    +                                                                      ~
    The '<' operator is reserved for future use.
    At C:\AzureStack_Installer\asdk-installer.ps1:870 char:53
    +   <summary class="btn-link" aria-haspopup="dialog" >
    +                                                     ~
    Missing file specification after redirection operator.
    Not all parse errors were reported.  Correct the reported errors and try again.
        + CategoryInfo          : ParserError: (:) [], ParseException
        + FullyQualifiedErrorId : MissingFileSpecification


    PS C:\Windows\System32> 

    Tuesday, July 31, 2018 12:26 PM
  • Hello,

    Can you download and install .NET 4.6 installer from here: .NET Framework 4.6  or   https://aka.ms/r6mkiy?

      

    And then run the following PowerShell command to validate your version of PowerShell:

     

    $PSVersionTable

     

    Once you have updated and validated your PowerShell version, please try running the installer again.

      

    -Make sure you are running PowerShell with elevated permissions

      

     

    Let us know how it goes.

         

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

    If you experience any issues with Azure Stack or the current ASDK release, please feel free to contact us.

                

     Thanks



    Gary Gallanes

    Tuesday, July 31, 2018 5:15 PM
  • Many thanks Gary.

    Below is what I see as of now.

    PS C:\Windows\System32> $PSVersionTable

    Name                           Value                                                             
    ----                           -----                                                             
    PSVersion                      5.1.14393.693                                                     
    PSEdition                      Desktop                                                           
    PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}                                           
    BuildVersion                   10.0.14393.693                                                    
    CLRVersion                     4.0.30319.42000                                                   
    WSManStackVersion              3.0                                                               
    PSRemotingProtocolVersion      2.3                                                               
    SerializationVersion           1.1.0.1                                                           



    PS C:\Windows\System32> 


    • Edited by sumitmahla Tuesday, July 31, 2018 10:32 PM
    Tuesday, July 31, 2018 10:25 PM
  • It is already installed. It gives me the message as below.

    .NET Framework 4.6 or a later update is already installed on this computer.

    Tuesday, July 31, 2018 10:31 PM
  • Thanks for the update.
    Azure Stack compatible Azure PowerShell modules are required to work with Azure Stack. Kindly ensure that you have the required modules installed as mentioned in this document: Install PowerShell for Azure Stack.

     

    Also, just to isolate the issue/as a test; you may consider rebooting your system and then re-try the operation. Are you experiencing a similar issue while invoking any other scripts? could you check if the script executes fine for you on another system?

    Wednesday, August 1, 2018 8:27 AM
  • I tried reboot few times. It does not help. Do we need to install azure stack power shell module even for "prepare your host" task of the azure stack dev kit installation?
    Wednesday, August 1, 2018 2:16 PM
  • Hello,

    No, the AzureStack & AzureRM PowerShell modules are not required to run the ASDK_Installer &  "prepare host" task.

      

    Please make sure you are running Server 2012 R2 or Server 2016 and running PowerShell as 'Administrator'.   Note: Server 2008 is not compatible with this deployment.

     

    Also - Can you run the following PowerShell to validate you are running PowerShell in 64bit and not 32bit?

     

    $Arch= (Get-Process -Id $PID).StartInfo.EnvironmentVariables["PROCESSOR_ARCHITECTURE"];

    if($Arch -eq 'x86') {

        Write-Host -Object 'Running 32-bit PowerShell';

    }

    elseif($Arch -eq 'amd64') {

        Write-Host -Object 'Running 64-bit PowerShell';

    }

        

    If that doesn't provide clues to resolve, try running the deployment checker tool to validate your environment.

    To validate your environment please run the Deployment Checker for Azure Stack

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

       

    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 ASDK release, feel free to contact us.

            

     Thanks, 



    Gary Gallanes




    Wednesday, August 1, 2018 7:48 PM
  • Many thanks Gary... It is running 64 bit.  Also I am running windows 2016 Datacenter edition. This is the same version which we get when we download asdk kit.

    PS C:\Windows\System32> $Arch= (Get-Process -Id $PID).StartInfo.EnvironmentVariables["PROCESSOR_ARCHITECTURE"];

    if($Arch -eq 'x86') {

        Write-Host -Object 'Running 32-bit PowerShell';

    }

    elseif($Arch -eq 'amd64') {

        Write-Host -Object 'Running 64-bit PowerShell';

    }
    Running 64-bit PowerShell

    PS C:\Windows\System32> 


    • Edited by sumitmahla Friday, August 3, 2018 2:22 AM
    Friday, August 3, 2018 1:52 AM
  • I ran deployment pre checker as well and it is all good.

    I think the github script is either old or corrupt.

     below is what I got after running prechecker.

    [ 18:28:56 ]  -- Check physical disks passed successfully. Note that ASDK handles situations where there is a pre-existing st
    orage pool, and will delete/recreate it.
    [ 18:28:56 ] Checking Memory...
    [ 18:28:56 ]  -- Memory on this server = 192
    [ 18:28:56 ]  -- System memory check passed successfully. ASDK requires a minimum of 96 GB of RAM, with 128 GB recommended.
    [ 18:28:56 ] Checking processor information...
    [ 18:28:58 ]  -- Number of CPU sockets = 2
    [ 18:28:58 ]  -- Number of physical cores =  24
    [ 18:28:58 ]  -- CPU socket count (2) and core count (12) meet the minimum requirements for ASDK.
    [ 18:28:58 ] Checking Hyper-V support on the host...
    [ 18:29:02 ]  -- This server supports the hardware virtualization required to enable Hyper-V.
    [ 18:29:02 ]  Checking free space for extracting the ASDK files...
    [ 18:29:02 ]  -- Listing disks and their free space

    DriveLetter FileSystemLabel       FileSystem DriveType HealthStatus OperationalStatus SizeRemaining      Size
    ----------- ---------------       ---------- --------- ------------ ----------------- -------------      ----
    C                                 NTFS       Fixed     Healthy      OK                    330.39 GB 446.13 GB
    D           SSS_X64FREE_EN-US_DV9 NTFS       Removable Healthy      OK                      1.09 GB    7.6 GB
                System Reserved       NTFS       Fixed     Healthy      OK                    169.26 MB    500 MB



    [ 18:29:02 ]  -- Free space check passed successfully.
    [ 18:29:02 ] SUCCESS : All of the prerequisite checks passed.
    [ 18:29:02 ] Deployment Checker has finished checking Azure Stack Development Kit requirements

    Tuesday, August 7, 2018 1:49 AM
  • Here is once again complete error I get.

    Interesting thing to note is is says something about py-3? Do we need python installed on windows? if so which version?I tried installing version 3.7 latest but still same issue.

    it also says in the error Missing file specification after redirection operator and also gives error "The '<' operator is reserved for future use." several times.

    PS C:\AzureStack_Installer> C:\AzureStack_Installer\asdk-installer.ps1
    At C:\AzureStack_Installer\asdk-installer.ps1:121 char:86
    + ... "Header header-logged-out  position-relative f4 py-3" role="banner" >
    +                                                                          ~
    Missing file specification after redirection operator.
    At C:\AzureStack_Installer\asdk-installer.ps1:136 char:21
    + </a>                </li>
    +                     ~
    The '<' operator is reserved for future use.
    At C:\AzureStack_Installer\asdk-installer.ps1:140 char:21
    + </a>                </li>
    +                     ~
    The '<' operator is reserved for future use.
    At C:\AzureStack_Installer\asdk-installer.ps1:145 char:21
    + </a>                </li>
    +                     ~
    The '<' operator is reserved for future use.
    At C:\AzureStack_Installer\asdk-installer.ps1:150 char:21
    + </a>                </li>
    +                     ~
    The '<' operator is reserved for future use.
    At C:\AzureStack_Installer\asdk-installer.ps1:154 char:21
    + </a>                </li>
    +                     ~
    The '<' operator is reserved for future use.
    At C:\AzureStack_Installer\asdk-installer.ps1:387 char:185
    + ... TF-8" method="post"><input name="utf8" type="hidden" value="&#x2713;" ...
    +                                                                 ~
    The ampersand (&) character is not allowed. The & operator is reserved for future use; wrap an ampersand in double quotation marks ("&") to pass it as part 
    of a string.
    At C:\AzureStack_Installer\asdk-installer.ps1:391 char:18
    + </form>          <h3 class="pt-2">Join GitHub today</h3>
    +                  ~
    The '<' operator is reserved for future use.
    At C:\AzureStack_Installer\asdk-installer.ps1:864 char:602
    + ... ureStack-Tools/commit/02301485f59a005c807e0c3991dbe0d5e098cb43">)</a>
    +                                                                      ~
    The '<' operator is reserved for future use.
    At C:\AzureStack_Installer\asdk-installer.ps1:870 char:53
    +   <summary class="btn-link" aria-haspopup="dialog" >
    +                                                     ~
    Missing file specification after redirection operator.
    Not all parse errors were reported.  Correct the reported errors and try again.
        + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
        + FullyQualifiedErrorId : MissingFileSpecification
     

    PS C:\AzureStack_Installer> 

    Tuesday, August 7, 2018 1:57 AM
  • Could you confirm if you are executing this script while we investigate this further?

    Tuesday, August 7, 2018 10:26 AM
  • Yes I am using the github code.

    Finally i was able run it but now got stuck at the below error:

    VERBOSE: Action: Status of 'Deployment-Phase0-DeployBareMetal' is 'Error'. - 8/9/2018 1:12:50 AM
    COMPLETE: Task Cloud - Deployment-Phase0-DeployBareMetal
    VERBOSE: Task: Status of action 'Deployment-Phase0-DeployBareMetal' of role 'Cloud' is 'Error'. -
    8/9/2018 1:12:50 AM
    VERBOSE: Step: Status of step 'PhysicalMachineAndInitialConfiguration - Phase 0 - Configure
    physical machine and external networking' is 'Error'. - 8/9/2018 1:12:50 AM
    VERBOSE: Checking if any of the in progress steps are complete. The following steps are currently
    in progress: 'PhysicalMachineAndInitialConfiguration'. - 8/9/2018 1:12:50 AM
    VERBOSE: Action: Action plan 'Deployment' failed. Finish running all steps that are currently in
    progress before exiting. - 8/9/2018 1:12:50 AM
    VERBOSE: Draining all steps that are still in progress. The following steps are still in progress
    or just completed: 'PhysicalMachineAndInitialConfiguration'. - 8/9/2018 1:12:50 AM
    VERBOSE: Action: Action plan 'Deployment' failed. - 8/9/2018 1:12:50 AM
    Invoke-EceAction : Action: Invocation of step PhysicalMachineAndInitialConfiguration failed.
    Stopping invocation of action plan.
    At line:5 char:2
    +  Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start Physi ...
    +  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], ActionExecutionException
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    PS C:\Windows\system32>

    Wednesday, August 8, 2018 9:06 PM
  • Thanks for the update. Try redeploying using the -rerun parameter.

    Ensure that you are running the deployment as under the AzureStack\AzureStackAdmin account and let us know the outcome.

     

    cd C:\CloudDeployment\setup

    .\InstallAzureStackPOC.ps1 -rerun

    Thursday, August 9, 2018 10:42 AM
  • It failed again with below error. What I also noticed is, the deployment chaneg my physical NIC configuration. Previously my physical NIC was configured with 10.X.X.174 and now the physical NIC has no IPv4 setting turned on. It is unchecked. Also there are couple of virtual Hyper V nic and out of these one, has the ip of 10.X.X.174. Is it expected beahviour?

       

    reStackAdmin - 8/9/2018 11:26:16 AM

    WARNING: Task: Invocation of interface 'Configure' of role 'Cloud\Infrastructure\BareMetal' failed


    Type 'Configure' of Role 'BareMetal' raised an exception:

    Fail to sync time from DC
    at <ScriptBlock>, <No file>: line 18 - 8/9/2018 11:26:16 AM
    Invoke-EceAction : Type 'Configure' of Role 'BareMetal' raised an exception:
    Fail to sync time from DC
    at <ScriptBlock>, <No file>: line 18
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:797 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OperationStopped: (Fail to sync time from DC:String) [Invoke-EceAc 
       tion], InterfaceInvocationFailedException
        + FullyQualifiedErrorId : Fail to sync time from DC,CloudEngine.Cmdlets.InvokeCmdlet

    VERBOSE: Step: Status of step 'PhysicalMachineAndInitialConfiguration.ConfigurePhysicalMachines - 
    (DEP) Configure Physical Machine' is 'Error'. - 8/9/2018 11:26:16 AM
    VERBOSE: Checking if any of the in progress steps are complete. The following steps are currently 
    in progress: 'PhysicalMachineAndInitialConfiguration.ConfigurePhysicalMachines'. - 8/9/2018 11:26:
    16 AM
    VERBOSE: Action: Action plan 'Deployment-Phase0-DeployBareMetal' failed. Finish running all steps 
    that are currently in progress before exiting. - 8/9/2018 11:26:16 AM
    VERBOSE: Draining all steps that are still in progress. The following steps are still in progress 
    or just completed: 'PhysicalMachineAndInitialConfiguration.ConfigurePhysicalMachines'. - 8/9/2018 
    11:26:16 AM
    VERBOSE: Action: Action plan 'Deployment-Phase0-DeployBareMetal' failed. - 8/9/2018 11:26:16 AM
    Invoke-EceAction : Action: Invocation of step 
    PhysicalMachineAndInitialConfiguration.ConfigurePhysicalMachines failed. Stopping invocation of 
    action plan.
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:797 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], ActionExecutionException
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    VERBOSE: Action: Status of 'Deployment-Phase0-DeployBareMetal' is 'Error'. - 8/9/2018 11:26:16 AM
    COMPLETE: Task Cloud - Deployment-Phase0-DeployBareMetal
    VERBOSE: Task: Status of action 'Deployment-Phase0-DeployBareMetal' of role 'Cloud' is 'Error'. - 
    8/9/2018 11:26:16 AM
    VERBOSE: Step: Status of step 'PhysicalMachineAndInitialConfiguration - Phase 0 - Configure physic
    al machine and external networking' is 'Error'. - 8/9/2018 11:26:16 AM
    VERBOSE: Checking if any of the in progress steps are complete. The following steps are currently 
    in progress: 'PhysicalMachineAndInitialConfiguration'. - 8/9/2018 11:26:16 AM
    VERBOSE: Action: Action plan 'Deployment' failed. Finish running all steps that are currently in p
    rogress before exiting. - 8/9/2018 11:26:16 AM
    VERBOSE: Draining all steps that are still in progress. The following steps are still in progress 
    or just completed: 'PhysicalMachineAndInitialConfiguration'. - 8/9/2018 11:26:16 AM
    VERBOSE: Action: Action plan 'Deployment' failed. - 8/9/2018 11:26:16 AM
    Invoke-EceAction : Action: Invocation of step PhysicalMachineAndInitialConfiguration failed. 
    Stopping invocation of action plan.
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:797 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], ActionExecutionException
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet




    PS C:\CloudDeployment\Setup> 

    Sunday, August 12, 2018 3:16 AM
  • Also on the deployment virtual hyper v nic, the preferred DNS server has been changed automatically to 192.168.200.67 and I can no longer ping www.google.com, so basically internet connectivity using dns names is gone.

    I can change it to my local dns server and make it work. Should I do that?

    Sunday, August 12, 2018 3:40 AM
  • Hello,

    To answer your question:

    “There are couple of virtual Hyper V nic and out of these one, has the ip of 10.X.X.174.

    Is it expected behavior?” - Yes

       

    Can you run the following PowerShell to validate your DNS settings and post the output back to this thread?

     

    ### Get IPConfig & DNS Forwarder from Host and AzS-DC01

    ipconfig /all

    ping 8.8.8.8

    TNC login.windows.net -Port 443

    New-PSSession -ComputerName AzS-DC01

    Enter-PSSession –ComputerName AzS-DC01

    ipconfig /all

    ping 8.8.8.8

    TNC login.windows.net -Port 443

    Get-DnsServerForwarder

       

    Also - To continue this investigation, please provide the following information:

      

    Build/Version:  

    Get-Content "C:\CloudDeployment\Configuration\Version\version.xml"

      

    Directory type: 

    Azure AD or ADFS

      

    Hardware: 

    How many CPU Cores, RAM, Get-Disk output

      

    Network: 

    Static or DHCP.

      

    The method used to access the Internet:

    NAT, Web Proxy, Transparent  Proxy, DMZ or Closed

      

    BareMetal or Nested Hyper-V:

      

    Deployment parameters used:

     

      

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

    If you experience any issues with Azure Stack or the current ASDK release, please feel free to contact us.

                

     Thanks



    Gary Gallanes


    Thursday, August 23, 2018 6:58 PM
  • Hello Gary,

    Super thanks for helping so far. I really appreciate this.

    I could not move ahead with this installation and decided to start fresh and record it installation. It is currently running but I believe it will fail. I will have recording available to exactly look at the installation process from start to finish. 

    Currently it is stuck on this from last 2 hours and I believe it will fail because external network connectivity is gone. I can't even ping the gateway IP. 

    First picture is where I had external connectivity only using IP but not using FQDN names. Second picture is where i lost all external connectivity. I can make recording available once it fails and recording stops.

    I can';t post pictures till my account if verified.

    Wednesday, September 12, 2018 2:52 AM
  • I believe my installation is failing due to NIC settings. Do we need any special settings on physical NIC card of the host?
    Wednesday, September 12, 2018 3:15 AM
  • I resolved one issue.

    I did a packet capture and could see that my azure stack host was continuously sending out arp request for gateway IP. it was receiving reply as well but for some reason it was not storing that reply in arp table. 

    I made a static entry and it started pinging gateway and internet ip 8.8.8.8.

    Now second problem is stil not solved. When I try to ping using dns names, I can't. What I did, I added my internal domain ip 10.61.X.10 as a secondary dns server on Deployment Hyper-V NIC and Management Hyper-V NIC. Still can't ping www.google.com

    Wednesday, September 12, 2018 4:30 AM
  • I did some further investigation.

    If I do a packet capture on Azure stack host physical NIC: and try to ping www.google.com, I see DNS request packets with source 192.168.200.65 to my DNS Server in Lab environment 10.61.X.10.

    During initial installation, I provided this IP as the DNS forwarder IP as I wanted Azure Stack to send DNS Forwarder request to 10.61.X.10. However as my per understanding, I should see this IP 192.168.200.65 natted to 10.61.0.174 before it sends the DNS request out to the network.

    Why is it sending request with 192.168.200.65? Upstream firewall in our network will block it.


    • Edited by sumitmahla Wednesday, September 12, 2018 5:06 AM
    Wednesday, September 12, 2018 5:06 AM
  • DNS forwarding just forwards the request to the new server, there should not be any NATtting that occurs. 

    You could unblock the IP address of your stack environment. 

    Wednesday, September 12, 2018 9:32 PM
  • ok will allow upstream firewall. However I still want to do it the right way.

    I have one physical NIC for upstream networking. This physical NIC will carry traffic from BGPNAT instance which will have an IP from the range 10.61.0.X and 192.168.200.X (DNS Traffic from AzureStack DNS VM). 

    So my question is:

    1. How can I make sure the 192.168.200.67 (IP of Stack DNS Virtual Machine) uses a vlan id when it sends traffic upstreams

    2. Same question for 10.61.0.X. 

    In the ASDK Deployment section there is an option to choose vlan id for BGPNAT01 instance. That will help for point 2. However How can I make it work for 192.168.200.67?

    Should I do it on Hyper-V Virtual NIC or should I go into Hyper-V Virtual Switch to do it?

    I want to make sure when upstream switch receives the traffic on trunk port, it gets the traffic with Vlan ID.

    Thursday, September 13, 2018 1:24 AM
  • I tried a fresh install by resolving network connectivity problem (by adding static arp entry on the stack host for upstream gateway and by opening up firewall to allow Stack DNS server to reach internet)

    However I am getting now storage cluster deployment error: Below is the error.. Please help.


    VERBOSE: [Storage:Deployment] Create the Storage Cluster - 9/16/2018 1:14:06 PM
    VERBOSE: [Storage:Deployment] Get-NetworkMap: BEGIN on SST-AZSTACK as AZURESTACK\AzureStackAdmin - 9/16/2018 1:14:06 PM
    VERBOSE: [Storage:Deployment] Get Network Map for nodes SST-AZSTACK - 9/16/2018 1:14:06 PM
    VERBOSE: [Storage:Deployment] Test-NetworkMap: BEGIN on SST-AZSTACK as AZURESTACK\AzureStackAdmin - 9/16/2018 1:14:06 PM
    VERBOSE: [Storage:Deployment] Find out which NICs are able to connect on each node. - 9/16/2018 1:14:06 PM
    VERBOSE: [Storage:Deployment] + SST-AZSTACK | Storage1 - 9/16/2018 1:14:20 PM
    VERBOSE: [Storage:Deployment] + SST-AZSTACK | Deployment - 9/16/2018 1:14:30 PM
    VERBOSE: [Storage:Deployment] + SST-AZSTACK | Management - 9/16/2018 1:14:34 PM
    VERBOSE: [Storage:Deployment] Test-NetworkMap: END on SST-AZSTACK as AZURESTACK\AzureStackAdmin - 9/16/2018 1:14:34 PM
    VERBOSE: [Storage:Deployment] Get-NetworkMap: END on SST-AZSTACK as AZURESTACK\AzureStackAdmin - 9/16/2018 1:14:34 PM
    VERBOSE: [Storage:Deployment] Creating the Storage cluster s-cluster.azurestack.local with hosts SST-AZSTACK and IP - 192.168.200.66. - 9/16/2018 1:14:3
    4 PM
    WARNING: Task: Invocation of interface 'Deployment' of role 'Cloud\Infrastructure\Storage' failed: 

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

    There was an error adding node 'SST-AZSTACK' to the cluster
    at New-MasCluster, C:\CloudDeployment\Classes\Storage\StorageHelpers.psm1: line 169
    at Deployment, C:\CloudDeployment\Classes\Storage\Storage.psm1: line 191
    at <ScriptBlock>, <No file>: line 39
    at <ScriptBlock>, <No file>: line 37 - 9/16/2018 1:14:35 PM
    WARNING: Task: Retrying interface 'Deployment' of role 'Cloud\Infrastructure\Storage'... - 9/16/2018 1:14:35 PM
    VERBOSE: Task: Running interface 'Deployment' of role 'Cloud\Infrastructure\Storage'. Attempt #2. totalRetries = 2 (Retry 1 of 2.) - 9/16/2018 1:14:35 P
    M
    VERBOSE: Wait for 60 seconds before attempting retry. - 9/16/2018 1:14:35 PM
    STARTING: Task Cloud\Infrastructure\Storage - Deployment
    VERBOSE: Interface: Path to module: C:\CloudDeployment\Classes\Storage\Storage.psm1 - 9/16/2018 1:15:35 PM
    VERBOSE: Interface: Running interface Deployment (Classes\Storage\Storage.psm1, Storage:Deployment) - 9/16/2018 1:15:35 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:15:37 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'DscHelper' include unapproved verbs that might make them less discove
    rable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Ge
    t-Verb. - 9/16/2018 1:15:47 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:15:47 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:15:48 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:15:48 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:15:48 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'DscHelper' include unapproved verbs that might make them less discove
    rable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Ge
    t-Verb. - 9/16/2018 1:15:54 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'DscHelper' include unapproved verbs that might make them less discove
    rable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Ge
    t-Verb. - 9/16/2018 1:15:56 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:15:56 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'CommonNC' include unapproved verbs that might make them less discover
    able. 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. - 9/16/2018 1:15:56 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:15:56 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:15:56 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:15:56 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'DscHelper' include unapproved verbs that might make them less discove
    rable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Ge
    t-Verb. - 9/16/2018 1:15:56 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:15:56 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'DscHelper' include unapproved verbs that might make them less discove
    rable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Ge
    t-Verb. - 9/16/2018 1:16:00 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:16:00 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:16:02 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:16:02 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'Domain' include unapproved verbs that might make them less discoverab
    le. 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-V
    erb. - 9/16/2018 1:16:02 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:16:02 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'VhdWim' include unapproved verbs that might make them less discoverab
    le. 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-V
    erb. - 9/16/2018 1:16:02 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'AzureStackPXE' include unapproved verbs that might make them less dis
    coverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, typ
    e Get-Verb. - 9/16/2018 1:16:02 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:16:02 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:16:02 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'DscHelper' include unapproved verbs that might make them less discove
    rable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Ge
    t-Verb. - 9/16/2018 1:16:02 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'UpdateNC' include unapproved verbs that might make them less discover
    able. 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. - 9/16/2018 1:16:02 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'AzureStackPXE' include unapproved verbs that might make them less dis
    coverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, typ
    e Get-Verb. - 9/16/2018 1:16:18 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'DscHelper' include unapproved verbs that might make them less discove
    rable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Ge
    t-Verb. - 9/16/2018 1:16:18 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:16:18 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'VhdWim' include unapproved verbs that might make them less discoverab
    le. 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-V
    erb. - 9/16/2018 1:16:18 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'DscHelper' include unapproved verbs that might make them less discove
    rable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Ge
    t-Verb. - 9/16/2018 1:16:20 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:16:20 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'OEM' 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
    . - 9/16/2018 1:16:20 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'UpdateNC' include unapproved verbs that might make them less discover
    able. 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. - 9/16/2018 1:16:20 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'AzureStackPXE' include unapproved verbs that might make them less dis
    coverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, typ
    e Get-Verb. - 9/16/2018 1:16:20 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'DscHelper' include unapproved verbs that might make them less discove
    rable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Ge
    t-Verb. - 9/16/2018 1:16:20 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'UpdatePhysicalMachineHelper' 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 appro
    ved verbs, type Get-Verb. - 9/16/2018 1:16:20 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:16:20 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'Storage' include unapproved verbs that might make them less discovera
    ble. 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. - 9/16/2018 1:16:20 PM
    VERBOSE: [Storage:Deployment] Storage prefix: SU1 - 9/16/2018 1:16:20 PM
    VERBOSE: [Storage:Deployment] Finding nuget package Microsoft.AzureStack.Fabric.Storage.SCPSModule from store C:\CloudDeployment\NuGetStore - 9/16/2018 
    1:16:22 PM
    VERBOSE: [Storage:Deployment] Searching for providers in the file path C:\CloudDeployment\NuGetStore. - 9/16/2018 1:16:24 PM
    VERBOSE: [Storage:Deployment] Using the provider 'NuGet' for searching packages. - 9/16/2018 1:16:24 PM
    VERBOSE: [Storage:Deployment] Total package yield:'1' for the specified package 'Microsoft.AzureStack.Fabric.Storage.SCPSModule'. - 9/16/2018 1:16:24 PM
    VERBOSE: [Storage:Deployment] Opening nuget package C:\CloudDeployment\NuGetStore\Microsoft.AzureStack.Fabric.Storage.SCPSModule.1.1.79.3.nupkg - 9/16/2
    018 1:16:24 PM
    VERBOSE: [Storage:Deployment] Copying 1 files from content\JEAPSRC to C:\Users\AzureStackAdmin\AppData\Local\Temp\hedn0igc.xal - 9/16/2018 1:16:24 PM
    VERBOSE: [Storage:Deployment] Closing nuget package - 9/16/2018 1:16:24 PM
    VERBOSE: [Storage:Deployment] JEA storage endpoint:  StorageEndpoint.1.1.79.3 - 9/16/2018 1:16:24 PM
    VERBOSE: [Storage:Deployment] Check for existing storage cluster 's-cluster.azurestack.local'. - 9/16/2018 1:16:24 PM
    VERBOSE: [Storage:Deployment] 
    Storage Cluster Name: s-cluster.azurestack.local 
    Scale-Out File Server: SU1FileServer 
    List of Cluster hosts: SST-AZSTACK - 9/16/2018 1:16:24 PM
    VERBOSE: [Storage:Deployment] Getting the pool configuration XML document - 9/16/2018 1:16:24 PM
    VERBOSE: [Storage:Deployment] Select cluster s-cluster which is in ProvisioningInProgress - 9/16/2018 1:16:24 PM
    VERBOSE: [Storage:Deployment] Updating domain account names for share permission configuration - 9/16/2018 1:16:24 PM
    VERBOSE: [Storage:Deployment] Clean up the AD computer object SU1FileServer and its DNS record - 9/16/2018 1:16:25 PM
    VERBOSE: [Storage:Deployment] Removing DNS resource record for name 'SU1FileServer' with IP 'True' under zone name 'azurestack.local' on the domain cont
    roller 'AzS-DC01'. - 9/16/2018 1:16:25 PM
    VERBOSE: [Storage:Deployment] Record for 'True' (A) not present. - 9/16/2018 1:16:27 PM
    VERBOSE: [Storage:Deployment] Removing DNS resource record for name 'SU1FileServer' with IP 'True' under zone name 'azurestack.local' on the domain cont
    roller 'AzS-DC01'. - 9/16/2018 1:16:27 PM
    VERBOSE: [Storage:Deployment] Record for 'True' (AAAA) not present. - 9/16/2018 1:16:27 PM
    VERBOSE: [Storage:Deployment] Clean up the AD computer object s-cluster and its DNS record - 9/16/2018 1:16:27 PM
    VERBOSE: [Storage:Deployment] Removing DNS resource record for name 's-cluster' with IP 'True' under zone name 'azurestack.local' on the domain controll
    er 'AzS-DC01'. - 9/16/2018 1:16:27 PM
    VERBOSE: [Storage:Deployment] Record for 'True' (A) not present. - 9/16/2018 1:16:27 PM
    VERBOSE: [Storage:Deployment] Removing DNS resource record for name 's-cluster' with IP 'True' under zone name 'azurestack.local' on the domain controll
    er 'AzS-DC01'. - 9/16/2018 1:16:27 PM
    VERBOSE: [Storage:Deployment] Record for 'True' (AAAA) not present. - 9/16/2018 1:16:27 PM
    VERBOSE: [Storage:Deployment] 
    Storage pool SU1_Pool 
     capacity tier percent:  
     reserve capacity for rebuild: 1 - 9/16/2018 1:16:27 PM
    VERBOSE: [Storage:Deployment]   Override tiering with Mirror - 9/16/2018 1:16:27 PM
    VERBOSE: [Storage:Deployment]   Volume SU1_Volume - 9/16/2018 1:16:27 PM
    VERBOSE: [Storage:Deployment] Prepare all storage nodes before creating new cluster - 9/16/2018 1:16:27 PM
    VERBOSE: [Storage:Deployment] Creating a JEA session to the cluster - 9/16/2018 1:16:27 PM
    VERBOSE: [Storage:Deployment] Connecting to JEA endpoint StorageEndpoint.1.1.79.3 on SST-AZSTACK - 9/16/2018 1:16:27 PM
    VERBOSE: [Storage:Deployment] Resetting storage node SST-AZSTACK before creating storage cluster - 9/16/2018 1:16:39 PM
    VERBOSE: [Storage:Deployment] Clearing storage node SST-AZSTACK - 9/16/2018 1:16:39 PM
    VERBOSE: [Storage:Deployment] Cleared storage node SST-AZSTACK - 9/16/2018 1:16:39 PM
    VERBOSE: [Storage:Deployment] fsutil behavior set DisableDeleteNotify 1 - 9/16/2018 1:16:39 PM
    VERBOSE: [Storage:Deployment] NTFS DisableDeleteNotify = 1 - 9/16/2018 1:16:39 PM
    VERBOSE: [Storage:Deployment] Checking for valid Roles/Features installation/configuration - 9/16/2018 1:16:39 PM
    VERBOSE: [Storage:Deployment] (Checking feature FS-FileServer ... ) - 9/16/2018 1:16:39 PM
    VERBOSE: [Storage:Deployment] (Checking feature Failover-Clustering ... ) - 9/16/2018 1:16:39 PM
    VERBOSE: [Storage:Deployment] Completed reset of storage node SST-AZSTACK - 9/16/2018 1:16:39 PM
    VERBOSE: [Storage:Deployment] Validate the cluster nodes before creating the cluster. - 9/16/2018 1:16:39 PM
    VERBOSE: [Storage:Deployment] Performing cluster validation on nodes SST-AZSTACK. - 9/16/2018 1:16:39 PM
    VERBOSE: [Storage:Deployment] - Skipping the cluster validation S2D disk checks in this one-node environment. - 9/16/2018 1:16:39 PM
    VERBOSE: [Storage:Deployment] Invoking Test-Cluster - 9/16/2018 1:16:39 PM
    WARNING: [Storage:Deployment] Cluster validation completed, but had a few tests either unselected/cancelled/deemed not applicable. Refer to the validati
    on report for more information  - 9/16/2018 1:16:57 PM
    VERBOSE: [Storage:Deployment] Validating number of disks meets minimum requirement : 3 - 9/16/2018 1:16:57 PM
    VERBOSE: [Storage:Deployment] Validation completed - Passed. Number of disks found is 4 - 9/16/2018 1:16:59 PM
    VERBOSE: [Storage:Deployment] Create the Storage Cluster - 9/16/2018 1:16:59 PM
    VERBOSE: [Storage:Deployment] Get-NetworkMap: BEGIN on SST-AZSTACK as AZURESTACK\AzureStackAdmin - 9/16/2018 1:16:59 PM
    VERBOSE: [Storage:Deployment] Get Network Map for nodes SST-AZSTACK - 9/16/2018 1:16:59 PM
    VERBOSE: [Storage:Deployment] Test-NetworkMap: BEGIN on SST-AZSTACK as AZURESTACK\AzureStackAdmin - 9/16/2018 1:16:59 PM
    VERBOSE: [Storage:Deployment] Find out which NICs are able to connect on each node. - 9/16/2018 1:16:59 PM
    VERBOSE: [Storage:Deployment] + SST-AZSTACK | Storage1 - 9/16/2018 1:17:12 PM
    VERBOSE: [Storage:Deployment] + SST-AZSTACK | Deployment - 9/16/2018 1:17:21 PM
    VERBOSE: [Storage:Deployment] + SST-AZSTACK | Management - 9/16/2018 1:17:26 PM
    VERBOSE: [Storage:Deployment] Test-NetworkMap: END on SST-AZSTACK as AZURESTACK\AzureStackAdmin - 9/16/2018 1:17:26 PM
    VERBOSE: [Storage:Deployment] Get-NetworkMap: END on SST-AZSTACK as AZURESTACK\AzureStackAdmin - 9/16/2018 1:17:26 PM
    VERBOSE: [Storage:Deployment] Creating the Storage cluster s-cluster.azurestack.local with hosts SST-AZSTACK and IP - 192.168.200.66. - 9/16/2018 1:17:2
    6 PM
    WARNING: Task: Invocation of interface 'Deployment' of role 'Cloud\Infrastructure\Storage' failed: 

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

    There was an error adding node 'SST-AZSTACK' to the cluster
    at New-MasCluster, C:\CloudDeployment\Classes\Storage\StorageHelpers.psm1: line 169
    at Deployment, C:\CloudDeployment\Classes\Storage\Storage.psm1: line 191
    at <ScriptBlock>, <No file>: line 39
    at <ScriptBlock>, <No file>: line 37 - 9/16/2018 1:17:26 PM
    WARNING: Task: Retrying interface 'Deployment' of role 'Cloud\Infrastructure\Storage'... - 9/16/2018 1:17:26 PM
    VERBOSE: Task: Running interface 'Deployment' of role 'Cloud\Infrastructure\Storage'. Attempt #3. totalRetries = 2 (Retry 2 of 2.) - 9/16/2018 1:17:26 P
    M
    VERBOSE: Wait for 60 seconds before attempting retry. - 9/16/2018 1:17:26 PM
    STARTING: Task Cloud\Infrastructure\Storage - Deployment
    VERBOSE: Interface: Path to module: C:\CloudDeployment\Classes\Storage\Storage.psm1 - 9/16/2018 1:18:26 PM
    VERBOSE: Interface: Running interface Deployment (Classes\Storage\Storage.psm1, Storage:Deployment) - 9/16/2018 1:18:26 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:18:28 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'DscHelper' include unapproved verbs that might make them less discove
    rable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Ge
    t-Verb. - 9/16/2018 1:18:39 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:18:39 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:18:39 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:18:39 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:18:39 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'DscHelper' include unapproved verbs that might make them less discove
    rable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Ge
    t-Verb. - 9/16/2018 1:18:45 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'DscHelper' include unapproved verbs that might make them less discove
    rable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Ge
    t-Verb. - 9/16/2018 1:18:47 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:18:47 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'CommonNC' include unapproved verbs that might make them less discover
    able. 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. - 9/16/2018 1:18:47 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:18:47 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:18:47 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:18:47 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'DscHelper' include unapproved verbs that might make them less discove
    rable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Ge
    t-Verb. - 9/16/2018 1:18:47 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:18:47 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'DscHelper' include unapproved verbs that might make them less discove
    rable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Ge
    t-Verb. - 9/16/2018 1:18:51 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:18:51 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:18:53 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:18:53 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'Domain' include unapproved verbs that might make them less discoverab
    le. 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-V
    erb. - 9/16/2018 1:18:53 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:18:53 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'VhdWim' include unapproved verbs that might make them less discoverab
    le. 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-V
    erb. - 9/16/2018 1:18:53 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'AzureStackPXE' include unapproved verbs that might make them less dis
    coverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, typ
    e Get-Verb. - 9/16/2018 1:18:53 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:18:53 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:18:53 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'DscHelper' include unapproved verbs that might make them less discove
    rable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Ge
    t-Verb. - 9/16/2018 1:18:53 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'UpdateNC' include unapproved verbs that might make them less discover
    able. 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. - 9/16/2018 1:18:53 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'AzureStackPXE' include unapproved verbs that might make them less dis
    coverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, typ
    e Get-Verb. - 9/16/2018 1:19:08 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'DscHelper' include unapproved verbs that might make them less discove
    rable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Ge
    t-Verb. - 9/16/2018 1:19:08 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:19:08 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'VhdWim' include unapproved verbs that might make them less discoverab
    le. 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-V
    erb. - 9/16/2018 1:19:08 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'DscHelper' include unapproved verbs that might make them less discove
    rable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Ge
    t-Verb. - 9/16/2018 1:19:10 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:19:10 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'OEM' 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
    . - 9/16/2018 1:19:10 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'UpdateNC' include unapproved verbs that might make them less discover
    able. 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. - 9/16/2018 1:19:10 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'AzureStackPXE' include unapproved verbs that might make them less dis
    coverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, typ
    e Get-Verb. - 9/16/2018 1:19:10 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'DscHelper' include unapproved verbs that might make them less discove
    rable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Ge
    t-Verb. - 9/16/2018 1:19:10 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'UpdatePhysicalMachineHelper' 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 appro
    ved verbs, type Get-Verb. - 9/16/2018 1:19:11 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'RoleHelpers' include unapproved verbs that might make them less disco
    verable. 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. - 9/16/2018 1:19:11 PM
    WARNING: [Storage:Deployment] The names of some imported commands from the module 'Storage' include unapproved verbs that might make them less discovera
    ble. 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. - 9/16/2018 1:19:11 PM
    VERBOSE: [Storage:Deployment] Storage prefix: SU1 - 9/16/2018 1:19:11 PM
    VERBOSE: [Storage:Deployment] Finding nuget package Microsoft.AzureStack.Fabric.Storage.SCPSModule from store C:\CloudDeployment\NuGetStore - 9/16/2018 
    1:19:14 PM
    VERBOSE: [Storage:Deployment] Searching for providers in the file path C:\CloudDeployment\NuGetStore. - 9/16/2018 1:19:15 PM
    VERBOSE: [Storage:Deployment] Using the provider 'NuGet' for searching packages. - 9/16/2018 1:19:15 PM
    VERBOSE: [Storage:Deployment] Total package yield:'1' for the specified package 'Microsoft.AzureStack.Fabric.Storage.SCPSModule'. - 9/16/2018 1:19:15 PM
    VERBOSE: [Storage:Deployment] Opening nuget package C:\CloudDeployment\NuGetStore\Microsoft.AzureStack.Fabric.Storage.SCPSModule.1.1.79.3.nupkg - 9/16/2
    018 1:19:15 PM
    VERBOSE: [Storage:Deployment] Copying 1 files from content\JEAPSRC to C:\Users\AzureStackAdmin\AppData\Local\Temp\vf2u2aib.bks - 9/16/2018 1:19:15 PM
    VERBOSE: [Storage:Deployment] Closing nuget package - 9/16/2018 1:19:15 PM
    VERBOSE: [Storage:Deployment] JEA storage endpoint:  StorageEndpoint.1.1.79.3 - 9/16/2018 1:19:15 PM
    VERBOSE: [Storage:Deployment] Check for existing storage cluster 's-cluster.azurestack.local'. - 9/16/2018 1:19:15 PM
    VERBOSE: [Storage:Deployment] 
    Storage Cluster Name: s-cluster.azurestack.local 
    Scale-Out File Server: SU1FileServer 
    List of Cluster hosts: SST-AZSTACK - 9/16/2018 1:19:15 PM
    VERBOSE: [Storage:Deployment] Getting the pool configuration XML document - 9/16/2018 1:19:15 PM
    VERBOSE: [Storage:Deployment] Select cluster s-cluster which is in ProvisioningInProgress - 9/16/2018 1:19:15 PM
    VERBOSE: [Storage:Deployment] Updating domain account names for share permission configuration - 9/16/2018 1:19:15 PM
    VERBOSE: [Storage:Deployment] Clean up the AD computer object SU1FileServer and its DNS record - 9/16/2018 1:19:16 PM
    VERBOSE: [Storage:Deployment] Removing DNS resource record for name 'SU1FileServer' with IP 'True' under zone name 'azurestack.local' on the domain cont
    roller 'AzS-DC01'. - 9/16/2018 1:19:16 PM
    VERBOSE: [Storage:Deployment] Record for 'True' (A) not present. - 9/16/2018 1:19:18 PM
    VERBOSE: [Storage:Deployment] Removing DNS resource record for name 'SU1FileServer' with IP 'True' under zone name 'azurestack.local' on the domain cont
    roller 'AzS-DC01'. - 9/16/2018 1:19:18 PM
    VERBOSE: [Storage:Deployment] Record for 'True' (AAAA) not present. - 9/16/2018 1:19:18 PM
    VERBOSE: [Storage:Deployment] Clean up the AD computer object s-cluster and its DNS record - 9/16/2018 1:19:18 PM
    VERBOSE: [Storage:Deployment] Removing DNS resource record for name 's-cluster' with IP 'True' under zone name 'azurestack.local' on the domain controll
    er 'AzS-DC01'. - 9/16/2018 1:19:18 PM
    VERBOSE: [Storage:Deployment] Record for 'True' (A) not present. - 9/16/2018 1:19:18 PM
    VERBOSE: [Storage:Deployment] Removing DNS resource record for name 's-cluster' with IP 'True' under zone name 'azurestack.local' on the domain controll
    er 'AzS-DC01'. - 9/16/2018 1:19:18 PM
    VERBOSE: [Storage:Deployment] Record for 'True' (AAAA) not present. - 9/16/2018 1:19:18 PM
    VERBOSE: [Storage:Deployment] 
    Storage pool SU1_Pool 
     capacity tier percent:  
     reserve capacity for rebuild: 1 - 9/16/2018 1:19:18 PM
    VERBOSE: [Storage:Deployment]   Override tiering with Mirror - 9/16/2018 1:19:18 PM
    VERBOSE: [Storage:Deployment]   Volume SU1_Volume - 9/16/2018 1:19:18 PM
    VERBOSE: [Storage:Deployment] Prepare all storage nodes before creating new cluster - 9/16/2018 1:19:18 PM
    VERBOSE: [Storage:Deployment] Creating a JEA session to the cluster - 9/16/2018 1:19:18 PM
    VERBOSE: [Storage:Deployment] Connecting to JEA endpoint StorageEndpoint.1.1.79.3 on SST-AZSTACK - 9/16/2018 1:19:18 PM
    VERBOSE: [Storage:Deployment] Resetting storage node SST-AZSTACK before creating storage cluster - 9/16/2018 1:19:30 PM
    VERBOSE: [Storage:Deployment] Clearing storage node SST-AZSTACK - 9/16/2018 1:19:30 PM
    VERBOSE: [Storage:Deployment] Cleared storage node SST-AZSTACK - 9/16/2018 1:19:30 PM
    VERBOSE: [Storage:Deployment] fsutil behavior set DisableDeleteNotify 1 - 9/16/2018 1:19:30 PM
    VERBOSE: [Storage:Deployment] NTFS DisableDeleteNotify = 1 - 9/16/2018 1:19:30 PM
    VERBOSE: [Storage:Deployment] Checking for valid Roles/Features installation/configuration - 9/16/2018 1:19:30 PM
    VERBOSE: [Storage:Deployment] (Checking feature FS-FileServer ... ) - 9/16/2018 1:19:30 PM
    VERBOSE: [Storage:Deployment] (Checking feature Failover-Clustering ... ) - 9/16/2018 1:19:30 PM
    VERBOSE: [Storage:Deployment] Completed reset of storage node SST-AZSTACK - 9/16/2018 1:19:30 PM
    VERBOSE: [Storage:Deployment] Validate the cluster nodes before creating the cluster. - 9/16/2018 1:19:30 PM
    VERBOSE: [Storage:Deployment] Performing cluster validation on nodes SST-AZSTACK. - 9/16/2018 1:19:30 PM
    VERBOSE: [Storage:Deployment] - Skipping the cluster validation S2D disk checks in this one-node environment. - 9/16/2018 1:19:30 PM
    VERBOSE: [Storage:Deployment] Invoking Test-Cluster - 9/16/2018 1:19:30 PM
    WARNING: [Storage:Deployment] Cluster validation completed, but had a few tests either unselected/cancelled/deemed not applicable. Refer to the validati
    on report for more information  - 9/16/2018 1:19:47 PM
    VERBOSE: [Storage:Deployment] Validating number of disks meets minimum requirement : 3 - 9/16/2018 1:19:47 PM
    VERBOSE: [Storage:Deployment] Validation completed - Passed. Number of disks found is 4 - 9/16/2018 1:19:49 PM
    VERBOSE: [Storage:Deployment] Create the Storage Cluster - 9/16/2018 1:19:49 PM
    VERBOSE: [Storage:Deployment] Get-NetworkMap: BEGIN on SST-AZSTACK as AZURESTACK\AzureStackAdmin - 9/16/2018 1:19:49 PM
    VERBOSE: [Storage:Deployment] Get Network Map for nodes SST-AZSTACK - 9/16/2018 1:19:49 PM
    VERBOSE: [Storage:Deployment] Test-NetworkMap: BEGIN on SST-AZSTACK as AZURESTACK\AzureStackAdmin - 9/16/2018 1:19:49 PM
    VERBOSE: [Storage:Deployment] Find out which NICs are able to connect on each node. - 9/16/2018 1:19:49 PM
    VERBOSE: [Storage:Deployment] + SST-AZSTACK | Storage1 - 9/16/2018 1:20:02 PM
    VERBOSE: [Storage:Deployment] + SST-AZSTACK | Deployment - 9/16/2018 1:20:11 PM
    VERBOSE: [Storage:Deployment] + SST-AZSTACK | Management - 9/16/2018 1:20:16 PM
    VERBOSE: [Storage:Deployment] Test-NetworkMap: END on SST-AZSTACK as AZURESTACK\AzureStackAdmin - 9/16/2018 1:20:16 PM
    VERBOSE: [Storage:Deployment] Get-NetworkMap: END on SST-AZSTACK as AZURESTACK\AzureStackAdmin - 9/16/2018 1:20:16 PM
    VERBOSE: [Storage:Deployment] Creating the Storage cluster s-cluster.azurestack.local with hosts SST-AZSTACK and IP - 192.168.200.66. - 9/16/2018 1:20:1
    6 PM
    WARNING: Task: Invocation of interface 'Deployment' of role 'Cloud\Infrastructure\Storage' failed: 

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

    There was an error adding node 'SST-AZSTACK' to the cluster
    at New-MasCluster, C:\CloudDeployment\Classes\Storage\StorageHelpers.psm1: line 169
    at Deployment, C:\CloudDeployment\Classes\Storage\Storage.psm1: line 191
    at <ScriptBlock>, <No file>: line 39
    at <ScriptBlock>, <No file>: line 37 - 9/16/2018 1:20:17 PM
    Invoke-EceAction : There was an error adding node 'SST-AZSTACK' to the cluster
        The computer 'sst-azstack.azurestack.local' is joined to a cluster.
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:809 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [Invoke-EceAction], InterfaceInvocationFailedException
        + FullyQualifiedErrorId : New-Cluster,Microsoft.FailoverClusters.PowerShell.NewClusterCommand,CloudEngine.Cmdlets.InvokeCmdlet
    VERBOSE: Step: Status of step 'PhysicalMachineAndInitialConfiguration.19 - (STO) Configure Storage Cluster' is 'Error'. - 9/16/2018 1:20:17 PM
    VERBOSE: Checking if any of the in progress steps are complete. The following steps are currently in progress: 'PhysicalMachineAndInitialConfiguration.1
    9'. - 9/16/2018 1:20:17 PM
    VERBOSE: Action: Action plan 'Deployment-Phase0-DeployBareMetal' failed. Finish running all steps that are currently in progress before exiting. - 9/16/
    2018 1:20:17 PM
    VERBOSE: Draining all steps that are still in progress. The following steps are still in progress or just completed: 'PhysicalMachineAndInitialConfigura
    tion.19'. - 9/16/2018 1:20:17 PM
    VERBOSE: Action: Action plan 'Deployment-Phase0-DeployBareMetal' failed. - 9/16/2018 1:20:17 PM
    Invoke-EceAction : Action: Invocation of step PhysicalMachineAndInitialConfiguration.19 failed. Stopping invocation of action plan.
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:809 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], ActionExecutionException
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    VERBOSE: Action: Status of 'Deployment-Phase0-DeployBareMetal' is 'Error'. - 9/16/2018 1:20:17 PM
    COMPLETE: Task Cloud - Deployment-Phase0-DeployBareMetal
    VERBOSE: Task: Status of action 'Deployment-Phase0-DeployBareMetal' of role 'Cloud' is 'Error'. - 9/16/2018 1:20:17 PM
    VERBOSE: Step: Status of step 'PhysicalMachineAndInitialConfiguration - Phase 0 - Configure physical machine and external networking' is 'Error'. - 9/16
    /2018 1:20:17 PM
    VERBOSE: Checking if any of the in progress steps are complete. The following steps are currently in progress: 'PhysicalMachineAndInitialConfiguration'.
     - 9/16/2018 1:20:17 PM
    VERBOSE: Action: Action plan 'Deployment' failed. Finish running all steps that are currently in progress before exiting. - 9/16/2018 1:20:17 PM
    VERBOSE: Draining all steps that are still in progress. The following steps are still in progress or just completed: 'PhysicalMachineAndInitialConfigura
    tion'. - 9/16/2018 1:20:17 PM
    VERBOSE: Action: Action plan 'Deployment' failed. - 9/16/2018 1:20:17 PM
    Invoke-EceAction : Action: Invocation of step PhysicalMachineAndInitialConfiguration failed. Stopping invocation of action plan.
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:809 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], ActionExecutionException
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet




    PS C:\CloudDeployment\Setup> 

      
    Sunday, September 16, 2018 1:51 PM
  • I would start by re-running the Deployment checker for Azure Stack script, and carefully review the Deployment planning document to make sure that your disks are correct and in the proper state before installing. 
    Thursday, September 20, 2018 11:26 PM