We have an issue after deploying/updating a service fabric cluster (ARM).After the successful deployment (i.e. New-AzureRmResourceGroupDeployment completes without error), the Service Fabric-Cluster portal correctly shows service fabric version 6.0.232.9494 (as defined in the ARM template). On the other hand, Service Fabric Explorershows all System services (such as ClusterMangerServices) with the previous service fabric version 5.7.207.9494.How long does it take until Service Fabric Explorer shows the correct cluster version?Any help would be appreciated.Regards, A. Hi Adam- InPrivate has no effect.- PS Get-Service Fabric Registered Cluster Config Version returnsConfigVersion-12345678How ever, we have the impression that we are dealing with a timeout. The intention of this ARM template update was:1. Update to the most recent service fabric version 6.0.232.94942.

1. Allora And The Broken Portal Set Up Events 2016

Swap cluster certificates (actually added the second certificate the first time )After 'New-AzureRmResourceGroupDeployment' (incremental) commandlet completedwithout any errors, the portal activity log on the resource group being updated shows the following:As you can see, some activities are not completed and the overall duration exceeds two hours.Might it have something to do with?A.UPDATE: After deploying the same ARM template again, the expected service fabric version 6.0.232.9494 is now also visible in Service Fabric Explorer. Apparently, installing a new second certificate and swapping it with the previous one atthe same time causes a timeout so that parts of the deployment process do not properly complete. We are pretty sure, that the above mentioned issue 392 addresses the same problem. Any way, it looks good now.My advice: First update the service fabric version, then swap certificates with another incremental deployment.

Allora And The Broken Portal Set Up Events 2016

@Adam: If you would like to get more details about our environment, please send me a direct email.Thanks, A.