search

microsoft / service-fabric

Service Fabric is a distributed systems platform for packaging, deploying, and managing stateless and stateful distributed applications and containers at large scale.
https://docs.microsoft.com/en-us/azure/service-fabric/
MIT License
3.03k stars 401 forks source link

VS 2017 Unable to deploy/debug to local cluster after update from SDK 6.2.283 to 6.2.301 or 6.3.176 #737

Open charristti opened 6 years ago

charristti commented 6 years ago

After upgrading service fabric sdk to 6.2.301 I can no longer deploy/debug service fabric applications to the local cluster. Environment is VS 2017 15.7.4 running on Windows 10 insider preview 1803. Reverting to 6.2.283 restores functionality.

Visual Studio Output Window shows:

9>Started executing script 'GetApplicationExistence'.
9>Finished executing script 'GetApplicationExistence'.
9>Time elapsed: 00:00:00.9494808
9>Started executing script 'Set-LocalClusterReady'.
9>powershell -NonInteractive -NoProfile -WindowStyle Hidden -ExecutionPolicy Bypass -Command "Import-Module 'C:\Program Files\Microsoft SDKs\Service Fabric\Tools\Scripts\DefaultLocalClusterSetup.psm1'; Set-LocalClusterReady -createOneNodeCluster $true"
9>Launching Service Fabric Local Cluster Manager...
9>You can use Service Fabric Local Cluster Manager (system tray application) to manage your local dev cluster.
9>Finished executing script 'Set-LocalClusterReady'.
9>Time elapsed: 00:00:01.2269469
9>Started executing script 'GetApplicationExistence'.
9>Finished executing script 'GetApplicationExistence'.
9>Time elapsed: 00:00:00.9774300
9>Started executing script 'GetApplicationExistence'.
9>Finished executing script 'GetApplicationExistence'.
9>Time elapsed: 00:00:01.0554773
9>Unable to determine whether the application is installed on the cluster or not
========== Build: 3 succeeded, 0 failed, 14 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========

Using powershell to run DevClusterSetup.ps1 gives: 2018-07-04_22-16-21

Comparing C:\SfDevCluster\Data\clusterManifest.xml, C:\SfDevCluster\Data\FabricHostSettings.xml, and C:\Users\charris\AppData\Local\Temp\CHARRIS-DEVPC75-Server-ScaleMin.xml for 6.2.283 vs 6.2.301 shows that 6.2.301 uses the machine name of the development computer while 6.2.283 uses localhost for the following entries.

clusterManifest.xml

<Infrastructure>
    <WindowsServer IsScaleMin="true">
      <NodeList>
        <Node NodeName="_Node_0" IPAddressOrFQDN="CHARRIS-DEVPC75" IsSeedNode="true" NodeTypeRef="NodeType0" FaultDomain="fd:/0" UpgradeDomain="0" />
      </NodeList>
    </WindowsServer>
  </Infrastructure>

FabricHostSettings.xml

<Section Name="Votes">
    <Parameter Name="_Node_0" Value="SeedNode,CHARRIS-DEVPC75:19002" />
  </Section>
  <Section Name="SeedNodeClientConnectionAddresses">
    <Parameter Name="_Node_0" Value="CHARRIS-DEVPC75:19000" />
</Section>

CHARRIS-DEVPC75-Server-ScaleMin.xml

<Infrastructure>
    <WindowsServer IsScaleMin="true">
      <NodeList>
        <Node NodeName="_Node_0" IPAddressOrFQDN="CHARRIS-DEVPC75" IsSeedNode="true" NodeTypeRef="NodeType0" FaultDomain="fd:/0" UpgradeDomain="0" />
      </NodeList>
    </WindowsServer>
</Infrastructure>

Stopping Service Fabric Host Service, changing machine name to LOCALHOST, and restarting service restores functionality in VS 2017 as long as cluster is NOT reset or reconfigured.

WIndows Event Log Entries

ServiceFabricIssues.txt

charristti commented 6 years ago

Any progress on this issue?? Issue continues on Windows 10 Pro Version 1809 17758.4 with service fabric runtime 6.3.176.9494 / sdk 3.2.176.9494.

Appears to work properly on Windows 10 Pro Version 1803 17134.286 at this time.

mikkelhegn commented 6 years ago

Please check this issue: https://github.com/Azure/service-fabric-issues/issues/1056