This release includes stability fixes as described in this document.
This update will only be available through manual upgrades. Clusters set to automatic upgrades will not receive this update unless toggled to manual.
The following packages and versions are part of this release:
| Service | Platform | Version |
|---|---|---|
| Service Fabric Runtime | Ubuntu 16 Ubuntu 18 Windows |
7.2.476.1 7.2.476.1804 7.2.477.9590 |
| Service Fabric for Windows Server | Service Fabric Standalone Installer Package | 7.2.477.9590 |
| .NET SDK | Windows .NET SDK Microsoft.ServiceFabric Reliable Services and Reliable Actors ASP.NET Core Service Fabric integration |
4.2.477 7.2.477 4.2.477 4.2.477 |
| Java SDK | Java for Linux SDK | 1.0.6 |
| Service Fabric PowerShell and CLI | AzureRM PowerShell Module SFCTL |
0.3.15 11.0.0 |
Microsoft Azure Service Fabric 7.2 Seventh Refresh Release Notes
- Support for Service Fabric 7.1 will be extended until July 31st, 2021.
- Key Vault references for Service Fabric applications are now GA on Windows and Linux.
- .NET 5 apps for Windows on Service Fabric are now supported as a preview.
- .NET 5 apps for Linux on Service Fabric will be added in the Service Fabric 8.0 release.
- Service Fabric 7.2 and higher runtime drops support for .NET Core Service Fabric apps running with .NET Core 2.2 runtime. .NET Core runtime 2.2 is out of support from Dec 2019. Service Fabric runtime will not install .NET Core runtime 2.2 as part of its dependency. Customers should upgrade their .NET 2.2 runtime SF apps to the next .NET Core LTS version 3.1.
- .NET Core runtime LTS 2.1 runtime will go out of support from Aug 21, 2021. Service Fabric releases after that date will drop support for Service Fabric apps running with .NET Core 2.1 runtime. Service Fabric .NET SDK will take a dependency on .Net runtime 3.* features to support Service Fabric .NET Core apps. This has no impact on Service Fabric .NET Framework SDK.
- Support for Windows Server 2016 and Windows 10 Server 1809 will be discontinued in future Service Fabric releases. We recommend updating your cluster VMs to Windows Server 2019.
| Versions | IssueType | Description | Resolution |
|---|---|---|---|
| Windows 7.2.457.9590 | Bug | Encoding scheme is not correct for authentication with Docker when using REST API's | Brief desc: Container Image downloading failed for some passwords when using basic authentication to download docker images. This was caused due to using an incorrect base64url encoding that Docker REST API's require. Impact:Container image downloading failed with certain passwords that were specified in SF ApplicationManifest files. Workaround: Change the password that you use to authenticate to your container registry (most likely Azure Container Registry). Attempt image download via Service Fabric. Continue to change password until it works. Due to encoding issues, some passwords will work, others will not. Fix: Corrected the code to use base64url encoding instead of just base64 encoding. |
| Windows 7.2.457.9590 | Bug | Improve sfpkg download resilient in network transient error | Brief desc: Downloading SFPKG from web endpoint is subject to network error. Service Fabric runtime changed web client to retry errors by SocketException. Impact: Application provisioning with SFPKG could fail by transient error. Workaround: Retry to provision SFPKG. Fix: Add retrying exceptions. |
| Windows 7.2.457.9590 | Bug | Detect the mismatch of data and image section | Brief desc: Node shutdown in parallel to image download can lead to files filled with zero. Impact: Impact in application instance folder is not auto-recovered at next download retry. Impact in Fabric package results in fabric upgrade error. Workaround: N/A Fix: Downloaded image overwrites files in destination path to reset the content. |
| Windows 7.2.457.9590 | Bug | Resolution issues when using fragments in URI | Brief desc: Passing an escaped URI fragment without using query strings would cause Reverse Proxy to incorrectly return an error. Reverse Proxy can now handle escaped URI fragments without query strings. Impact: Reverse Proxy (FabricApplicationGateway) would incorrectly return FABRIC_E_SERVICE_DOES_NOT_EXIST when using an escaped URI fragment without a query string. Workaround: Modify connecting code to not use escaped URI fragments or pass in a dummy query string. Fix: Support handling escaped URI fragments correctly in Reverse Proxy, with or without query strings. |
| Windows 7.2.457.9590 | Bug | Handle receiving pings when using WebSocket connections | Brief desc: Connecting to Reverse Proxy through WebSockets and sending pings would cause Reverse Proxy to crash. Reverse Proxy can now handle receiving WebSocket pings without crashing. Impact: Reverse Proxy (FabricApplicationGateway) would crash after receiving a ping when using WebSocket connections. Workaround: Modify connecting code to stop sending pings. Fix: Support handling ping actions in Reverse Proxy. |
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: