10 KiB
Microsoft Azure Service Fabric 7.2 Fourth Refresh Release Notes
This release includes stability fixes as described in this document.
Due to the holiday season, this update will only be available through manual upgrades. Clusters set to automatic upgrades will not receive this update unless toggled to manual. The Linux release is now also available.
The following packages and versions are part of this release:
| Service | Platform | Version |
|---|---|---|
| Service Fabric Runtime | Ubuntu 16 Ubuntu 18 Windows |
7.2.447.1 7.2.447.1804 7.2.445.9590 |
| Service Fabric for Windows Server | Service Fabric Standalone Installer Package | 7.2.445.9590 |
| .NET SDK | Windows .NET SDK Microsoft.ServiceFabric Reliable Services and Reliable Actors ASP.NET Core Service Fabric integration |
4.2.445 7.2.445 4.2.445 4.2.445 |
| Java SDK | Java for Linux SDK | 1.0.6 |
| Service Fabric PowerShell and CLI | AzureRM PowerShell Module SFCTL |
0.3.15 10.0.0 |
Content
Microsoft Azure Service Fabric 7.2 Fourth Refresh Release Notes
Key Announcements
- .NET 5 apps for Windows on Service Fabric are now supported as a preview. Look out for the GA announcement of .NET 5 apps for Windows on Service Fabric in the coming weeks.
- .NET 5 apps for Linux on Service Fabric will be added in the Service Fabric 8.0 release.
- Windows Server 20H2 is now supported as of the 7.2 CU4 release.
Update to certificate selection logic
Starting with Service Fabric 7.2 CU4, and for all future SF versions, the logic the runtime uses to select the Cluster certificate has changed. This change applies to both clusters with certificates declared by common name, and clusters with certificates declared by thumbprint when Security/UseSecondaryIfNewer setting is set to true.
Previously, Service Fabric selected among the pool of declared certificates, the certificate that was the farthest living (i.e. the largest NotAfter value). Starting in this CU, Service Fabric will select the most recently issued certificate (i.e. the largest NotBefore value).
In certain configurations, this upgrade will cause a change to the cluster certificate. In general this change should have no impact on cluster health. However, if clients of Service Fabric expect Service Fabric to present the previous certificate, they may need to be updated to expect the new certificate (or any valid cluster certificate).
Read more here
Breaking Changes
- 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.
Upcoming Breaking Changes
- .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 1809 will be discontinued in future Service Fabric releases. We recommend updating your cluster VMs to Windows Server 2019.
Service Fabric Common Bug Fixes
| Versions | IssueType | Description | Resolution |
|---|---|---|---|
| Windows 7.1.458.9590 | Bug | Add report code 167 to HealthReport handler | Brief desc: Applications which declare endpoint certificates that do not exist on the node will cause a crash in the SF runtime on Linux. Impact: SF applications deployed to Linux clusters which declare non-existent endpoint certificates. Workaround: Ensure that certificates declared in application manifests exist on the nodes where the application may be deployed. Fix: The health report raised for this scenario was not handled, and entered a code path which crashed the host process. |
| Windows 7.1.458.9590 | Bug | Version-less KVRef should be explicitly blocked | Brief desc: Only versioned Key Vault objects of object type 'secret' are supported for SF Key Vault References: Read more about key vault objects. Impact: Previously version-less objects were allowed to deploy, but have undefined behavior; this fix blocks these deployments. Workaround: N/A Fix: Any app using a version-less reference can transition to versioned by upgrading to the object marked "latest" in key-vault explicitly, and using the 'secret' object-type version of that object. You will need to upgrade the app before upgrading the cluster version. |
| Windows 7.1.458.9590 | Bug | Deactivation should get blocked if the node has replica with FT in QL state | Brief desc: Node Deactivations from MR with intent RemoveNode/RemoveData will now get blocked if the node has a replica which is part of partition which is in Quorum Loss state. Impact: Any node deactivations (from MR jobs) or service fabric upgrades will get blocked when these conditions are met. Workaround: N/A Fix: Block these node deactivations when being performed for node which has replica whose partition is in Quorum Loss. This will prevent SF from approving destructive actions like RemoveNode/RemoveData for the service which has not recovered yet. |
| Windows 7.1.458.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.xml 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. |
Repositories and Download Links
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: