View known issues in Azure Stack HCI 2311.5 release
Applies to: Azure Stack HCI, version 23H2
This article identifies the critical known issues and their workarounds in the Azure Stack HCI 2311.5 release.
The release notes are continuously updated, and as critical issues requiring a workaround are discovered, they're added. Before you deploy your Azure Stack HCI, carefully review the information contained in the release notes.
Important
The production workloads are only supported on the Azure Stack HCI systems running the generally available 2311.2 release.
For more information about the new features in this release, see What's new in 23H2.
Issues for version 2311.5
This software release maps to software version number 10.2311.5.6. This release only supports updates from 2311 release.
Release notes for this version include the issues fixed in this release, known issues in this release, and release noted issues carried over from previous versions.
Fixed issues
Microsoft isn't currently aware of any fixed issues with this release.
Known issues in this release
Here are the known issues in this release:
| Feature | Issue | Workaround/Comments |
|---|---|---|
| Update | Download operations don't terminate after the specified timeout of 6 hours. | Microsoft is actively working to resolve this issue. If you encounter this issue, contact Microsoft Support for next steps. |
| Update | Update is in Failed state: DownloadFailed. Summary XML from ECE not present. | Microsoft is actively working to resolve this issue. If you encounter this issue, contact Microsoft Support for next steps. |
| Updates | When applying a cluster update to 10.2311.5.6 the Get-SolutionUpdate cmdlet may not respond and eventually fails with a RequestTimeoutException after approximately 10 minutes. This is likely to occur following an add or repair server scenario. |
Use the Start-ClusterGroup and Stop-ClusterGroup cmdlets to restart the update service. Get-ClusterGroup -Name "Azure Stack HCI Update Service Cluster Group" | Stop-ClusterGroup Get-ClusterGroup -Name "Azure Stack HCI Update Service Cluster Group" | Start-ClusterGroup A succesful run of these cmdlets should bring the update service online. |
Known issues from previous releases
Here are the known issues from previous releases:
| Feature | Issue | Workaround/Comments |
|---|---|---|
| Arc VM management | When a new node is added into the cluster, it fails with: Node add failed at ERROR: An older version of the Arc VM cluster extension is installed on your cluster. | Make sure you have the latest firewall requirements including endpoint https://hciarcvmscontainerregistry.azurecr.io on port 443. This endpoint is required for Azure Stack HCI Arc VM container registry. |
| Arc VM management | When you update to 10.2311.4.5, the arcbridge status shows "UpgradeFailed" on the Azure portal. | Make sure you have the latest firewall requirements including endpoint https://hciarcvmscontainerregistry.azurecr.io on port 443. This endpoint is required for Azure Stack HCI Arc VM container registry. |
| Arc VM management | Deployment or update of Arc Resource Bridge could fail when the automatically generated temporary SPN secret during this operation, starts with a hyphen. | Retry the deployment/update. The retry should regenerate the SPN secret and the operation will likely succeed. |
| Arc VM management | Arc Extensions on Arc VMs stay in "Creating" state indefinitely. | Sign in to the VM, open a command prompt, and type the following: Windows: notepad C:\ProgramData\AzureConnectedMachineAgent\Config\agentconfig.json Linux: sudo vi /var/opt/azcmagent/agentconfig.json Next, find the resourcename property. Delete the GUID that is appended to the end of the resource name, so this property matches the name of the VM. Then restart the VM. |
| Arc VM management | When a new server is added to an Azure Stack HCI cluster, storage path isn't created automatically for the newly created volume. | You can manually create a storage path for any new volumes. For more information, see Create a storage path. |
| Arc VM management | Restart of Arc VM operation completes after approximately 20 minutes although the VM itself restarts in about a minute. | There's no known workaround in this release. |
| Arc VM management | In some instances, the status of the logical network shows as Failed in Azure portal. This occurs when you try to delete the logical network without first deleting any resources such as network interfaces associated with that logical network. You should still be able to create resources on this logical network. The status is misleading in this instance. |
If the status of this logical network was Succeeded at the time when this network was provisioned, then you can continue to create resources on this network. |
| Arc VM management | In this release, when you update a VM with a data disk attached to it using the Azure CLI, the operation fails with the following error message: Couldn't find a virtual hard disk with the name. |
Use the Azure portal for all the VM update operations. For more information, see Manage Arc VMs and Manage Arc VM resources. |
| Deployment | There's a sporadic heartbeat reliability issue in this release due to which the registration encounters the error: HCI registration failed. Error: Arc integration failed. | This issue is intermittent. Try rerunning the deployment. For more information, see Rerun the deployment. |
| Deployment | There's an intermittent issue in this release where the Arc integration validation fails with this error: Validator failed. Can't retrieve the dynamic parameters for the cmdlet. PowerShell Gallery is currently unavailable. Please try again later. |
This issue is intermittent. Try rerunning the deployment. For more information, see Rerun the deployment. |
| Deployment | The AzureEdgeRemoteSupport extension shows as "Failed" in the cluster view and "Succeeded" in the node view. Additionally, the node view displays an incorrect extension name, "AzureEdgeEdgeRemoteSupport". | This issue is cosmetic and doesn't impact extension functionality. You may want to follow these steps to manually mitigate the issue: 1. In the Azure portal, navigate to the resource group for your nodes. 2. Go to each Arc node and uninstall the Remote Support extension. 3. Allow up to 12 hours for the Azure Stack HCI Resource Provider to update the extensions. This procedure enables the reinstallation of the extension, ensuring it displays the correct name, AzureEdgeRemoteSupport, and resolves any failures observed in the cluster view. Optionally, you can use the cmdlet sync-azurestackhci to force a sync on any of the cluster nodes. |
| Update | In rare instances, you may encounter this error while updating your Azure Stack HCI: Type 'UpdateArbAndExtensions' of Role 'MocArb' raised an exception: Exception Upgrading ARB and Extension in step [UpgradeArbAndExtensions :Get-ArcHciConfig] UpgradeArb: Invalid applianceyaml = [C:\AksHci\hci-appliance.yaml]. | If you see this issue, contact Microsoft Support to assist you with the next steps. |
| Update | In this release, there's a health check issue preventing a single server running Azure Stack HCI from being updated via the Azure portal. | Use PowerShell to perform your update. For more information, see Update your Azure Stack HCI, version 23H2 via PowerShell. |
| Networking | There's an infrequent DNS client issue in this release that causes the deployment to fail on a two-node cluster with a DNS resolution error: A WebException occurred while sending a RestRequest. WebException.Status: NameResolutionFailure. As a result of the bug, the DNS record of the second node is deleted soon after it's created resulting in a DNS error. | Restart the server. This operation registers the DNS record, which prevents it from getting deleted. |
| Azure portal | In some instances, the Azure portal might take a while to update and the view might not be current. | You might need to wait for 30 minutes or more to see the updated view. |
| Arc VM management | Deleting a network interface on an Arc VM from Azure portal doesn't work in this release. | Use the Azure CLI to first remove the network interface and then delete it. For more information, see Remove the network interface and see Delete the network interface. |
| Deployment | Providing the OU name in an incorrect syntax isn't detected in the Azure portal. The incorrect syntax is however detected at a later step during cluster validation. | There's no known workaround in this release. |
| Deployment | In some instances, running the Arc registration script doesn't install the mandatory extensions, Azure Edge device Management or Azure Edge Lifecycle Manager. | The workaround is to run the script again and make sure that all the mandatory extensions are installed before you Deploy via Azure portal. |
| Deployment | The first deployment step: Before Cloud Deployment when Deploying via Azure portal can take from 45 minutes to an hour to complete. | |
| Deployment | Deployments via Azure Resource Manager time out after 2 hours. Deployments that exceed 2 hours show up as failed in the resource group though the cluster is successfully created. | To monitor the deployment in the Azure portal, go to the Azure Stack HCI cluster resource and then go to new Deployments entry. |
| Azure Site Recovery | Azure Site Recovery can't be installed on an Azure Stack HCI cluster in this release. | There's no known workaround in this release. |
| Update | When updating the Azure Stack HCI cluster via the Azure Update Manager, the update progress and results may not be visible in the Azure portal. | To work around this issue, on each cluster node, add the following registry key (no value needed):New-Item -Path "HKLM:\SYSTEM\CurrentControlSet\Services\HciCloudManagementSvc\Parameters" -forceThen on one of the cluster nodes, restart the Cloud Management cluster group. Stop-ClusterGroup "Cloud Management"Start-ClusterGroup "Cloud Management"This won't fully remediate the issue as the progress details may still not be displayed for a duration of the update process. To get the latest update details, you can Retrieve the update progress with PowerShell. |
| Updates | In rare instances, if a failed update is stuck in an In progress state in Azure Update Manager, the Try again button is disabled. | To resume the update, run the following PowerShell command:Get-SolutionUpdate|Start-SolutionUpdate. |
| Updates | In some cases, SolutionUpdate commands could fail if run after the Send-DiagnosticData command. |
Make sure to close the PowerShell session used for Send-DiagnosticData. Open a new PowerShell session and use it for SolutionUpdate commands. |
| Updates | In rare instances, when applying an update from 2311.0.24 to 2311.2.4, cluster status reports In Progress instead of expected Failed to update. | Retry the update. If the issue persists, contact Microsoft Support. |
| Cluster aware updating | Resume node operation failed to resume node. | This is a transient issue and could resolve on its own. Wait for a few minutes and retry the operation. If the issue persists, contact Microsoft Support. |
| Cluster aware updating | Suspend node operation was stuck for greater than 90 minutes. | This is a transient issue and could resolve on its own. Wait for a few minutes and retry the operation. If the issue persists, contact Microsoft Support. |
| Security | In this release, if you enable Dynamic Root of Measurement (DRTM) using the Enable-AzSSecurity cmdlet, you receive the following error:DRTM setting is not supported on current release at C:\ProgramFiles\WindowsPowerShell\Modules\AzureStackOSConfigAgent\AzureStackOSConfigAgent psm1:4307 char:17 + ...throw "DRTM setting is not supported on current release". |
DRTM is not supported in this release. |
Next steps
- Read the Deployment overview.