Summary
-
Added TPM status monitor for physical hosts.
-
Re-enabled the ability to generate host crash dumps and trigger NMI crashes for hangs.
-
Fixed an issue in which a VM could undergo an additional restart on any VM operation if a restart operation was previously executed on it.
Fixes rolled up from previous hotfix releases
-
Addressed DNS server vulnerability described in CVE-2020-1350.
-
Changes that addressed cluster instability.
-
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.
-
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 an issue where internal secret rotation might not update the Network Controller credential, leading to a disconnect between the Azure Stack Hub hosts and Azure Stack Hub Network Controller.
-
Addressed an issue that can lead to a memory leak on the Azure Consistent Storage VMs, affecting Object Based Storage performance/stability.
-
Disabled NCHostAgentMonitor.
-
Improved the admin portal experience to show the download progress of Azure Stack Hub update packages.
-
Addressed an issue where setting the LicenseType of a VM to the value of None is not recognized as a valid LicenseType.
-
Addressed a performance issue with an inefficient lookup of VM metadata by their network identity.
-
Fixed an issue in which during an OEM or full update, certain infrastructure VMs can't be started after the host is re-imaged.
-
Fixed a performance issue in the Storage Resource Provider that can impact overall control plane actions.
-
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 update in certain conditions, the Disk Resource Provider may not correctly update.
-
Addressed issues where NonHAVMs may not start after an update.
Hotfix information
To apply this hotfix, you must have version 1.1908.4.33 or later.
Important As outlined in the Release Notes for the 1908 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.Download the zip file now.
More information
Azure Stack Hub update resources
Manage updates in Azure Stack overview
Monitor updates in Azure Stack by using the privileged endpoint
