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

Unable to deploy an Service Mesh application - "message": "Resource {0} not found.", #193

Open SamirFarhat opened 6 years ago

SamirFarhat commented 6 years ago

Since Sunday, i'm not be able to deploy a SM application :

Deployment failed. Correlation ID: 3df4a3be-4079-4596-8e03-d3d95895bd28. { "error": { "code": "NotFound", "message": "Resource {0} not found.", "details": [], "innerError": "Code: NotFound - System.Fabric.Wrp.Common.WrpException: Resource A7321EC3-3919-442B-8A85-3C8580527C41 not found.\r\n at Microsoft.ServiceFabric.Services.Communication.Client.ServicePartitionClient1.<InvokeWithRetryAsync>d__241.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at Microsoft.ServiceFabric.Services.Communication.Client.ServicePartitionClient1.<InvokeWithRetryAsync>d__26.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at Microsoft.SeaBreeze.NetworkResourceManager.Operation.Networks.PutNetworkOperation1.d8.MoveNext() in D:\agent_work\1\s\src\NetworkResourceManager\Operation\Networks\PutNetworkOperation.cs:line 57\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at Microsoft.SeaBreeze.NetworkResourceManager.Operation.Networks.PutNetworkOperation1.<ExecuteAsync>d__6.MoveNext() in D:\\agent_work\\1\\s\\src\\NetworkResourceManager\\Operation\\Networks\\PutNetworkOperation.cs:line 41\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Fabric.Wrp.Common.OperationBase1.d48.MoveNext() in D:\agent_work\1\s\src\Common\OperationBase.cs:line 108" } }

On the Activity Log of the Resource Group, it's clear the the Network Resource deployment is failing.

SamirFarhat commented 6 years ago

I'm finally able to deploy. The issue 2 is gone. The Resource {0} not found is due to incorrect Container Registry image name. The error message should be more explicit and clear.