Azure Stack Hub hotfix 1.2108.2.111

Article
09/21/2022

Summary

Fixed an issue in which some StorageController requests might time out under high concurrency.
Removed some of the network performance counters and reduced collection interval for other perf counters.
Cleaned up unneeded networking traces from Baremetal, NC and XRP VMs.
Fixed an issue deleting Microsoft.ContainerService/managedCluster resources that occurred when resources managed by the AKS resource provider were manually deleted beforehand.
Fixed a regression in which VM status is reported as UNKNOWN in the portal.

Fixes rolled up from previous hotfix releases

Fixed an issue that could impact updating from 2102 to 2108.
Support for new Kubernetes versions in AKS.
Fixed bugs in trace collector.
Fixed a bug related to physical disk health when repairing a node with SED drives.
Improvements to support tools.
Fixed bugs in log collection.
Fixed code defect leading to VM deployment failures.
Improved the resolution of the Network Resource Provider.
Fixed a bug in incremental disk snapshots in which a failed snapshot can block any future snapshot operations.
Fixed a disk snapshot failure and VM IO hang when taking snapshots.
Shortened the PEP tokens and made them human-readable.
Fix to improve SLB throughput after enabling Simultaneous Multi-Threading (SMT).
Fixed an issue in which the table service partition was offline when its underlying storage was out of space.
Added retry logic around Get-Volume calls in Test-AzureStack InfraCapacity validation.

Hotfix information

To apply this hotfix, you must have version 1.2108.2.65 or later.

Important

As outlined in the release notes for the 2108 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.