Skip to content
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.

Endpoint 'counterServiceListener' not referenced in network #74

Open
larrywa opened this issue Apr 23, 2019 · 0 comments
Open

Endpoint 'counterServiceListener' not referenced in network #74

larrywa opened this issue Apr 23, 2019 · 0 comments

Comments

@larrywa
Copy link

larrywa commented Apr 23, 2019

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

AzureFiles volume sample. Put in your storage account name/key etc and then do a local F5 debug in Visual Studio 2017.

Any log messages given by the failure

New-SFMeshResourceDeployment : 'counterApp.counterService': Endpoint 'counterServiceListener' not referenced in network
Refs.
At line:1 char:157

  • ... -SFCluster; New-SFMeshResourceDeployment -ResourceDescriptionList 'C: ...
  •             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    • CategoryInfo : NotSpecified: (:) [New-SFMeshResourceDeployment], ServiceFabricException
    • FullyQualifiedErrorId : DeployMeshResourcesErrorId,Microsoft.ServiceFabric.Powershell.Http.DeployMeshResourcesCm

Expected/desired behavior

Expected behavior is to be able to run this app locally after putting in all of the storage account information

OS and Version?

Windows 10 Enterprise 1803

Mention any other details that might be useful

Just trying to figure out why the name of the listener is listed in the service.yaml and gateway.yaml file but it is saying that the listener is not referenced in the network. What does that mean?


Thanks! We'll be in touch soon.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant