This release includes the bug fixes described in this document. This release includes runtime, SDKs and Windows Server Standalone deployments to run on-premises.
The following packages and versions are part of this release:
| Service | Platform | Version |
|---|---|---|
| Service Fabric Runtime | Ubuntu 16 Ubuntu 18 Windows |
8.1.323.1 8.1.323.1 8.1.321.9590 |
| Service Fabric for Windows Server | Service Fabric Standalone Installer Package | 8.1.321.9590 |
| .NET SDK | Windows .NET SDK Microsoft.ServiceFabric Reliable Services and Reliable Actors ASP.NET Core Service Fabric integration |
5.1.321 8.1.321 8.1.321 8.1.321 |
| Java SDK | Java for Linux SDK | 1.0.6 |
| Service Fabric PowerShell and CLI | AzureRM PowerShell Module SFCTL |
0.3.15 11.1.0 |
Microsoft Azure Service Fabric 8.1 First Refresh Release Notes
- Current And Upcoming Breaking Changes
- Service Fabric Common Bug Fixes
- Repositories and Download Links
-
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.
-
Guest executable and container applications created or upgraded in SF clusters with runtime versions 7.1+ are incompatible with prior SF runtime versions (e.g. SF 7.0).
Following scenarios are impacted:- An application with guest executables or containers is created or upgraded in an SF 7.1+ cluster.
The cluster is then downgraded to a previous SF runtime version (e.g. SF 7.0).
The application fails to activate. - A cluster upgrade from pre-SF 7.1 version to SF 7.1+ version is in progress.
In parallel with the SF runtime upgrade, an application with guest executables or containers is created or upgraded.
The SF runtime upgrade starts rolling back (due to any reason) to the pre-SF 7.1 version.
The application fails to activate.
To avoid issues when upgrading from a pre-SF 7.1 runtime version to an SF 7.1+ runtime version, do not create or upgrade applications with guest executables or containers while the SF runtime upgrade is in progress.
- The simplest mitigation, when possible, is to delete and recreate the application in SF 7.0.
- The other option is to upgrade the application in SF 7.0 (for example, with a version only change).
If the application is stuck in rollback, the rollback has to be first completed before the application can be upgraded again.
- An application with guest executables or containers is created or upgraded in an SF 7.1+ cluster.
- .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. This includes the following release versions and beyond - 8.0 CU4 and above, 8.1 CU2 and above and 8.2 RTO release and above. Current apps running on .NET Core 2.1 runtime will continue to work, but requests for investigations or request for changes will no longer be entertained. 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.
| Versions | IssueType | Description | Resolution |
|---|---|---|---|
| Windows - 8.1.321.9590 Ubuntu 16 - 8.1.323.1 Ubuntu 18 - 8.1.323.1 |
Bug | Upgrade of stateful and stateless services fail with Service DNS name in use error | Brief desc: Azure Service Fabric Service Update fails with DnsNameInUse if ServiceDnsName is set. Impact: Updating Service Fabric service via ARM is being blocked when ServiceDnsName is unchanged. This is blocking service update flows for some users. This is resulting from a new client parameterization that exposed an underlying behavior that blocked no-ops. Fix NamingService is now handling the ServiceDnsName parameter as a no-op when it is unchanged. Workaround Update service using Service Fabric PowerShell cmdlet Update-ServiceFabricService, omitting the ServiceDnsName parameter if it is unchanged. |
| Windows - 8.1.321.9590 Ubuntu 16 - 8.1.323.1 Ubuntu 18 - 8.1.323.1 |
Bug | NamingStoreService.RecoverPrimaryAsyncOperation keeps retrying rejected operations for codes such as DnsNameInUse | Brief desc: NamingService would perpetually retry a subset of rejected operations, which risks congesting the job pipeline. Impact: Naming StoreService may perpetually hold onto rejected operations and requeue them to the job queue. This happened for rejected operations that tried to override dns name of another service ErrorCodeValue::DnsNameInUse. Fix An extra filter has been added to discard rejected operations for known error codes. |
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: