title | description | author | ms.topic | ms.date | ms.author | ms.reviewer | ms.lastreviewed |
---|---|---|---|---|---|---|---|
Azure Stack Hub known issues |
Learn about known issues in Azure Stack Hub releases. |
sethmanheim |
article |
05/07/2024 |
sethm |
rtiberiu |
11/30/2023 |
This article lists known issues in Azure Stack Hub releases. The list is updated as new issues are identified.
To access known issues for a different version, use the version selector dropdown above the table of contents on the left.
::: moniker range=">=azs-2301"
Important
Review this article before applying the update.
::: moniker-end
::: moniker range="<azs-2301"
[!IMPORTANT]
If your Azure Stack Hub instance is behind by more than two updates, it's considered out of compliance. You must update to at least the minimum supported version to receive support.
::: moniker-end
::: moniker range="azs-2311"
- Applicable: This issue applies to release 2311 and later.
- Cause: Azure Kubernetes Service on Azure Stack Hub, currently in preview, is being discontinued and will not be released to general availability. If you try to register a new subscription to the Microsoft.Containerservice resource provider, the registration stays in the Registering state. If you try to create a new managed Kubernetes cluster or access existing managed Kubernetes clusters, you might see the raining cloud error screen.
- Remediation: Microsoft is aware of the problem and is working on a fix.
- Occurrence: Common.
- Applicable: This issue applies to release 2311.
- Cause: In some cases when you run the
Start-AzsCryptoWipe
command to shut down Azure Stack Hub, one of the physical machines is not powered off. - Remediation: If you see that any physical machine is not powered down, you must turn off that machine through the Baseboard Management Controller (BMC).
- Occurrence: Common.
- Applicable: This issue applies to release 2311 and later.
- Cause: The new OS build with 2311 introduces a new system alert for thin provisioning: an alert is raised when the storage pool usage exceeds 70%. Fixed-size volumes are used in the Azure Stack Hub deployment, so the 70% threshold is always exceeded. You can find this warning in the Test-AzureStack reports.
- Remediation: You can ignore the alert in the Test-AzureStack report. Microsoft is aware of the issue and is working on a fix.
- Occurrence: Common.
- Applicable: This issue applies to release 2311.
- Cause: In the Azure Stack Hub user portal, under the Virtual Networks section, there are three new options for virtual networks: DNS Servers, Flow Timeout, and BGP community string. You can successfully modify the DNS configuration using the DNS Servers option. However, attempts to use the Flow Timeout and BGP community string options result in a failure within the portal notifications. No changes are made to the underlying services; the errors are only in the portal.
- Remediation: Microsoft is aware of the problem and is working on a fix.
- Occurrence: Common.
- Applicable: This issue applies to release 2311 and later.
- Cause: Some users might see an error message with error code templateLinkAndJson when deploying an API application from the marketplace, even though the deployment was successful.
- Remediation: Check your API app after deployment to ensure deployment was successful. Microsoft is aware of the problem and is working on a fix.
- Occurrence: Common.
- Applicable: This issue applies to all Azure Stack Hub add-on resource providers.
- Cause: After secret rotation, the rotation state shows as "in progress" even though the rotation completed successfully, the provisioning state shows "successful," and the expiration date is updated.
- Remediation: None. No impact to your system or workloads.
- Occurrence: All supported versions of Azure Stack Hub.
::: moniker-end
::: moniker range="azs-2306"
- Applicable: This issue applies to all Azure Stack Hub add-on resource providers.
- Cause: After secret rotation, the rotation state shows as "in progress" even though the rotation completed successfully, the provisioning state shows "successful," and the expiration date is updated.
- Remediation: None. No impact to your system or workloads.
- Occurrence: All supported versions of Azure Stack Hub.
::: moniker-end
::: moniker range="azs-2301"
- Applicable: This issue applies to release 2301.
- Cause: The number of cores reported in the Azure Stack Hub admin portal in the cluster Nodes Capacity window is incorrect. This is cosmetic and an issue with a change in 2301 with respect to how the Fabric Resource Provider gets this information. This impacts both new deployments and existing stamps updating to 2301, but doesn't affect operation of the stamp or any workload deployments.
- Remediation: Microsoft is aware of the problem and is working on a fix.
- Occurrence: Minor portal issue that occurs consistently.
- Applicable: This issue applies to all Azure Stack Hub add-on resource providers.
- Cause: After secret rotation, the rotation state shows as "in progress" even though the rotation completed successfully, the provisioning state shows "successful," and the expiration date is updated.
- Remediation: None. No impact to your system or workloads.
- Occurrence: All supported versions of Azure Stack Hub.
::: moniker-end
::: moniker range="azs-2206"
::: moniker-end ::: moniker range="azs-2108"
::: moniker-end ::: moniker range="azs-2102"
::: moniker-end ::: moniker range="azs-2008"
::: moniker-end ::: moniker range="azs-2005"
::: moniker-end ::: moniker range="azs-2002"
::: moniker-end ::: moniker range="azs-1910"
::: moniker-end ::: moniker range="azs-1908"
::: moniker-end ::: moniker range="azs-1907"
::: moniker-end ::: moniker range="azs-1906"
::: moniker-end ::: moniker range="azs-1905"
::: moniker-end ::: moniker range="azs-1904"
::: moniker-end ::: moniker range="azs-1903"
::: moniker-end ::: moniker range="azs-1902"
::: moniker-end ::: moniker range="azs-1901"
::: moniker-end ::: moniker range="azs-1811"
::: moniker-end ::: moniker range="azs-1809"
::: moniker-end ::: moniker range="azs-1808"
::: moniker-end ::: moniker range="azs-1807"
::: moniker-end ::: moniker range="azs-1805"
::: moniker-end ::: moniker range="azs-1804"
::: moniker-end ::: moniker range="azs-1803"
::: moniker-end ::: moniker range="azs-1802"
::: moniker-end
::: moniker range="<azs-2301" You can access older versions of Azure Stack Hub known issues in the table of contents on the left side, under the Resources > Release notes archive. Select the desired archived version from the version selector dropdown in the upper left. These archived articles are provided for reference purposes only and do not imply support for these versions. For information about Azure Stack Hub support, see Azure Stack Hub servicing policy. For further assistance, contact Microsoft Customer Support Services. ::: moniker-end