Summary
-
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.
Fixes rolled up from previous hotfix releases
-
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.
Hotfix information
To apply this hotfix, you must have version 1.1910.0.58 or later.
Important As outlined in the Release Notes for the 1910 update, make sure that you refer to the update activity checklist on running Test-AzureStack (with specified parameters), and resolve any operational issues that are found, including all warnings and failures. Also, review active alerts and resolve any that require action.
File information
Download the following files. Then, follow the instructions on the Apply updates in Azure Stack page on the Microsoft Learn website to apply this update to Azure Stack.
More information
Azure Stack Hub update resources
Manage updates in Azure Stack overview
Monitor updates in Azure Stack by using the privileged endpoint
