- Improved extraction reliability by addressing idempotent/file locking issues.
- Host update reliability improvements by addressing the image locking issues.
- Improved orchestrator resiliency for the low memory situations on ERCS VMs.
- Fixed "out of memory exception" during internal secret rotation.
- Enhanced self-healing of update and repair operations when hard disk specialization fails unexpectedly.
Fixes rolled up from previous hotfix releases
- Corrected the mechanism used to detect expired or nearly expired external endpoint certificates to only verify the currently bound certificate, instead of all certificates in the certificate store.
- Addressed issues in the Network Controller host agent that can cause Software Defined Network (SDN) instability.
- Improved handling of Virtual Machine extensions and disk provisioning state.
- Addressed an issue that can lead to a memory leak on the Azure Consistent Storage VMs, affecting Object Based Storage performance and stability.
- Increased reliability for Compute Resource Provider updates.
- Improved monitoring and recovery of the RDAgent.
- Addressed additional cases where NonHAVMs may not start after an update.
- Improved reliability of VM disk resize operations.
- Addressed an issue where an incorrect data encryption key is used during key migration.
- Addressed an issue where an update is incorrectly reported as successful when it had actually failed.
- Improved reliability of the DiskRP update process.
- Updated host monitoring configurations to reduce overall system CPU load.
- Corrected an issue where tenant and admin portals fail to load because a resource provider is not responding.
- Improved the admin portal experience to show the download progress of Azure Stack Hub update packages.
- Added a bypass flag for the Privileged End Point command Set-bmccredential to address cases where the customer needs to set the BMC password independently from it being updated in the system configuration store.
- Corrected an issue where the compute resource provider causes elevated CPU load on systems with a large number of VMs deployed.
- Addressed an issue where setting the LicenseType of a VM to the value of None is not recognized as a valid LicenseType.
- Fixed an issue introduced in the 1910 release that impacts future servicing of Azure Stack Hub, which includes affecting the ability to take OEM updates or repair Azure Stack nodes.
- Fixed an issue in which filtering of Marketplace images in the Marketplace Management blade may be inconsistent.
- Fixed an issue in which the volume capacity in the Storage Capacity blade may show as not available or does not update.
- Fixed a performance issue in the Storage Resource Provider that can impact overall control plane actions.
- Fixed a performance issue in the Compute Resource Provider that can impact overall control plane actions.
- Fixed an issue in which a newly deployed VM might use the incorrect protocol in the Windows Azure Agent.
- Fixed an issue in which communications and data transfer to a resource behind an internal load balancer might be significantly impacted and subsequently time out.
- Fixed an issue in which during an OEM or full update, certain infrastructure VMs can't be started after the host is re-imaged.
- Increased reliability for Compute Resource Provider updates.
- Improved monitoring and recovery of the RDAgent.
- Addressed additional cases where NonHAVMs may not start after an update.
- Improved reliability of VM disk resize operations.
- Addressed an issue where an incorrect data encryption key is used during key migration.
- Addressed an issue where an update is incorrectly reported as successful when it had actually failed.
- Improved reliability of the DiskRP update process.