Azure / service-fabric-mesh-preview

Service Fabric Mesh is the Service Fabric's serverless offering to enable developers to deploy containerized applications without managing infrastructure. Service Fabric Mesh , aka project “SeaBreeze” is currently available in private preview. This repository will be used for tracking bugs/feature requests as GitHub issues and for maintaining the latest documentation.
MIT License
82 stars 13 forks source link

Error running TodoList Quickstart on Dev Cluster #233

Open tbertenshaw opened 6 years ago

tbertenshaw commented 6 years ago

I had the same issue running the asp.net core2 sample from the samples repo.

So I started again with dotnetcore2.1 and got the same result.

( I am using a local dev cluster (tried both 5 and 1 nodes) on Windows 2016 , and the latest version of the VS Service Fabric Mesh Tooling (0.90.20180718.1) and servicefabric sdk)

(here's my repo of this https://github.com/tbertenshaw/todolistapp)

This is on line 19 of the Index.cshtml.cs. (when debugging locally)

System.Net.Http.HttpRequestException HResult=0x80004005 Message=The requested name is valid, but no data of the requested type was found Source=System.Net.Http StackTrace: at System.Net.Http.ConnectHelper.d2.MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Threading.Tasks.ValueTask1.get_Result() at System.Net.Http.HttpConnectionPool.<CreateConnectionAsync>d__40.MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Threading.Tasks.ValueTask1.get_Result() at System.Net.Http.HttpConnectionPool.d45.MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Threading.Tasks.ValueTask1.get_Result() at System.Net.Http.HttpConnectionPool.<SendWithRetryAsync>d__37.MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1.ConfiguredTaskAwaiter.GetResult() at System.Net.Http.RedirectHandler.d4.MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult() at System.Net.Http.HttpClient.d62.MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult() at WebFrontEnd.Pages.IndexModel.OnGet() in c:\users\administrator\source\repos\todolistapp\WebFrontEnd\Pages\Index.cshtml.cs:line 19 at Microsoft.AspNetCore.Mvc.RazorPages.Internal.ExecutorFactory.VoidHandlerMethod.Execute(Object receiver, Object[] arguments) at Microsoft.AspNetCore.Mvc.RazorPages.Internal.PageActionInvoker.d__30.MoveNext()

Inner Exception 1: SocketException: The requested name is valid, but no data of the requested type was found

InnerException | {System.Net.Sockets.SocketException (11004): The requested name is valid, but no data of the requested type was found at System.Net.Http.ConnectHelper.ConnectAsync(String host, Int32 port, CancellationToken cancellationToken)} | System.Exception {System.Net.Sockets.SocketException}

tbertenshaw commented 6 years ago

if i put a breakpoint on line 19

the code continues without that error and returns a 200. So is there a dns issue then? Incidentally the same code runs ok on a windows 10 1806 machine

ChackDan commented 6 years ago

Ryan , please followup.

bjorkstromm commented 6 years ago

I had the same issue, problem was that Symantec Endpoint Protection (Network Threat Protection) is blocking requests.

This is not the first time Symantec Endpoint Protection breaks networking w/ Hyper-V and Docker for Windows.

tbertenshaw commented 6 years ago

@ChackDan assume this is still an issue and there are no current workarounds? As I paused my evaluation until i have a solution as was a bit of a blocker for me.

ChackDan commented 6 years ago

@tbertenshaw @mholo65 : understood. Thankyuou for you guys being patient with us.

tbertenshaw commented 6 years ago

Assume the latest 6.3CU1 isn't supposed to resolve this issue? As it still seems to be present for me after installing. Incidentally when this is addressed what is the solution likely to be in the form of? the SDK? the VS tooling or the Service Fabric runtime?

ChackDan commented 6 years ago

it would be a new SDK corresponding to the release 6.4 ETA third week of Sept.

tbertenshaw commented 6 years ago

don't suppose there is a preview of this or a unpleasant workaround i could utilise, so i can start evaluating it again prior to this release?

iamalexmang commented 6 years ago

+1 - still not working. :-(

ChackDan commented 6 years ago

Sorry, 6.4 is still being tested in our staging and test regions. we found regressions with the new features in the runtime and so at this time I do not have an ETA on the release. I hope we are able to release it in the new few weeks.

teun2408 commented 6 years ago

@ChackDan Do you have more information on the possible release date of the update?

ChackDan commented 6 years ago

I still do not have an ETA. We have now found issues with the isolated networks and traced the issue to the Windows Stack. and working on getting a fix from them, so that the runtime can be released.

magnuskarlssonhm commented 5 years ago

Could we have an update on this issue? We are moving to solution design in beginning of January and will not be able to move forward with Service Mesh if the product is not ready to build a POC with.

ConnorChristie commented 5 years ago

I am also interested in any updates on this... Running into the same issue on windows 10

vipul-modi commented 5 years ago

Can you check if you are able to use Visual Objects sample or that is running in the same issues or not. The 6.4 rollout is in progress.

magnuskarlssonhm commented 5 years ago

This error was due to my computers locale being sv-SE so I just changed it. I FIgured it out by changing service.yaml files cpu value from 0.5 to 0,5 and that solved it. Also changed CPU to 1. Now stuck at

SocketException: No such host is known
System.Net.Http.ConnectHelper.ConnectAsync(string host, int port, CancellationToken cancellationToken)

When I run the aplication in Visual studio, what does the IP address in the browser come from? What should it be? I thought it should be localhost but now it is an IP address.

vipul-modi commented 5 years ago

The IP address is the NAT address assigned to the container, docker inspect should return you that IP address.