Azure Service Fabric 8.1 Third Refresh Update (3.1) Release

This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.

Azure Service Fabric 8.1 Third Refresh Update (3.1) is now available!

The Azure Service Fabric 8.1 Third Refresh Update (3.1) release includes stability fixes for the runtime, standalone, and Azure environments.

This release will only be available through manual upgrades. Clusters set to automatic upgrades will not receive this release. For how to configure upgrades, please see classic or managed documentation.

 

Packages and Versions

  • Service Fabric Runtime
    • Ubuntu 16 - 8.1.340.1
    • Ubuntu 18 - 8.1.340.1
    • Windows - 8.1.337.9590
  • Service Fabric for Windows Server
    • Service Fabric Standalone Installer Package - 8.1.337.9590
  • .NET SDK
    • Windows .NET SDK - 5.1.337
    • Microsoft.ServiceFabric - 8.1.337
    • Reliable Services and Reliable Actors - 8.1.337
    • ASP.NET Core Service Fabric integration - 8.1.337
  • Java SDK
    • Java for Linux SDK - 1.0.6
  • Service Fabric PowerShell and CLI
    • AzureRM PowerShell Module - 0.3.15
    • SFCTL - 11.0.0

Current Breaking Changes

  • Guest Executable and Container Applications: Guest executable and container applications created or upgraded in Service Fabric clusters with runtime versions 7.1+ are incompatible with prior Service Fabric runtime versions (e.g. Service Fabric 7.0).
    Following scenarios are impacted:
    • An application with guest executables or containers is created or upgraded in an Service Fabric 7.1+ cluster.
      The cluster is then downgraded to a previous Service Fabric runtime version (e.g. Service Fabric 7.0).
      The application fails to activate.
    • A cluster upgrade from pre-SF 7.1 version to Service Fabric 7.1+ version is in progress.
      In parallel with the Service Fabric runtime upgrade, an application with guest executables or containers is created or upgraded.
      The Service Fabric 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 Service Fabric 7.1+ runtime version, do not create or upgrade applications with guest executables or containers while the Service Fabric runtime upgrade is in progress.
    • The simplest mitigation, when possible, is to delete and recreate the application in Service Fabric 7.0.
    • The other option is to upgrade the application in Service Fabric 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.
  • .NET Core 2.x Support: .NET Core runtime LTS 2.1 runtime is out of support as of Aug 21, 2021, and .NET Core runtime 2.2 is out of support from Dec 2019. Service Fabric releases after those dates will drop support for Service Fabric apps running with .NET Core 2.1, and .NET Core 2.2 runtimes respectively. Current apps running on .NET Core 2.x runtime will continue to work, but requests for investigations or request for changes will no longer receive support. Service Fabric .NET SDK will take a dependency on .NET runtime 3.x features to support Service Fabric .NET Core apps.
  • Ubuntu 16.04 Support: Ubuntu 16.04 LTS reached it's 5-year end-of-life window on April 30, 2021. Service Fabric runtime will drop support for Ubuntu 16.04 after that date as well. Current applications running on it will continue to work, but requests for investigations or requests for change will no longer receive support. We recommend moving your applications to Ubuntu 18.04.

For more details, please read the release notes.

REMEMBER: these articles are REPUBLISHED. Your best bet to get a reply is to follow the link at the top of the post to the ORIGINAL post! BUT you're more than welcome to start discussions here:

This site uses Akismet to reduce spam. Learn how your comment data is processed.