-
Notifications
You must be signed in to change notification settings - Fork 21
Publish from VS2017 got stuck in Copying application to image store... #821
Comments
The same trouble on Windows cluster. |
I think I've encountered this too when publishing from VS to Azure Windows cluster. As workaround removing the following parameter from publish profile fixed the issue for me:
|
@juho-hanhimaki |
Looks like there's some problem in ImageStore service. For now, I'm using an external store as a workaround. |
@hengyiliu . Thanks, i'll check. |
This seems similar to #813. We are currently investigating. |
Same problem here - it appears that attempting to uploading files larger than ~4MB hangs the transfer. |
I will close this issue as duplicate, and use #813 to track the fix. As I answered in #813 , this is due to a configuration mismatch between standalone and Azure clusters for MaxMessageSize configuration, which is 10 MB for standalone and only 4 MB for the cluster. It happens when the local cluster is set up on the client, which changes the default configuration to 10 MB. We will make a fix to ensure the 2 are in sync. Meanwhile, the mitigation is to remove the local cluster, then upload to the Azure cluster succeeds. |
VS2017 15.5.6
Azure Service Fabric on Linux: 6.1.183.1
Service Fabric SDK: 3.0.456.9494
I have a Azure Service Fabric cluster on Linux and a simple project created from VS template. When I publish from VS, it got stuck in "Copying application to image store..." for hours and won't complete:
Service Fabric explorer page showed nothing deployed. I have also tried to re-create a new project and a new cluster from Azure Portal, and still got stuck in the same place. It was working fine a few days ago. Has anything changed recently?
The text was updated successfully, but these errors were encountered: