This release includes bug fixes as described in this document.
The following packages and versions are part of this release:
| Service | Platform | Version |
|---|---|---|
| Service Fabric Runtime | Ubuntu 16 Ubuntu 18 Windows |
7.1.455.1 7.1.455.1804 7.1.459.9590 |
| Service Fabric for Windows Server | Service Fabric Standalone Installer Package | 7.1.458.9590 |
| .NET SDK | Windows .NET SDK Microsoft.ServiceFabric Reliable Services and Reliable Actors ASP.NET Core Service Fabric integration |
4.1.458 7.1.458 4.1.458 4.1.458 |
| Java SDK | Java for Linux SDK | 1.0.6 |
| Service Fabric PowerShell and CLI | AzureRM PowerShell Module SFCTL |
0.3.15 10.0.0 |
Microsoft Azure Service Fabric 7.1 Sixth Refresh Release Notes
| Versions | IssueType | Description | Resolution |
|---|---|---|---|
| Windows 7.1.459.9590 Ubuntu 1804 7.1.455.1804 Ubuntu 16 7.1.455 |
Bug | Impact to clusters using Open Network Feature | Brief desc: The scope of this issue is limited to the Azure Service Fabric clusters which use Open Network Feature. To improve security and availability, Azure infrastructure will make a breaking change that will affect the supported versions of Service Fabric. This release includes a fix for this issue and is made available in all regions. You will have to manually upgrade your clusters if you are affected. To enable cluster support for open network for containerized services, you should have the following properties enabled in your cluster and application manifest files. The following actions are required to determine if upgrade of Service Fabric runtime is required or not. You have the IPProviderEnabled setting set to true in your clusters, you have two options: 1) If you are NOT using open networking, then you can disable that setting, setting its value to "false". In the cluster manifest, in the "Hosting" section, look for IPProviderEnabled and set it to false and upgrade the cluster. 2) If you are using "open networking", then you need to upgrade to this version which includes fix for security breaking change. Impact: Nodes won't be able to start and the Service Fabric cluster won't come up if you don't upgrade to this patch release at the time the underlying infrastructure is updated. Workaround: N/A Fix: Upgrade to this version as soon as possible. |
The table below is an overview of the direct links to the packages associated with this release. Follow this guidance for setting up your developer environment: