Sync release-ash-2501 with main, fix merge

Sync release-ash-2501 with main, fix merge

Author: sethmanheim

azure-stack/operator/azure-stack-servicing-policy.md

@@ -4,7 +4,7 @@ titleSuffix: Azure Stack Hub
 description: Learn about the Azure Stack Hub servicing policy and how to keep an integrated system in a supported state.
 author: sethmanheim
 ms.topic: article
-ms.date: 10/24/2024
+ms.date: 10/30/2024
 ms.author: sethm
 ms.lastreviewed: 03/18/2020
 
@@ -46,9 +46,9 @@ Find documentation on how to plan for and manage updates, and how to determine y
 
 For information about a specific update, including how to download it, see the release notes for that update:
 
+- [Azure Stack Hub 2501 update](./release-notes.md?view=azs-2501&preserve-view=true)
 - [Azure Stack Hub 2408 update](./release-notes.md?view=azs-2408&preserve-view=true)
 - [Azure Stack Hub 2406 update](./release-notes.md?view=azs-2406&preserve-view=true)
-- [Azure Stack Hub 2311 update](./release-notes.md?view=azs-2311&preserve-view=true)
 
 ## Hotfixes
 
@@ -78,11 +78,11 @@ You must also have an active support agreement with the hardware partner that ma
 
 Hotfixes aren't considered major update versions. 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 (N-2) to receive support.
 
-For example, if the most recent update version available is 2408 (N), the two previous update versions were 2406 and 2311, which means both 2406 (N-1) and 2311 (N-2) remain in support. However, the 2306 (and earlier) version is out of support, as 2306 was N-3 when the 2408 update was released. For the current release of Azure Stack Hub, the following versions are considered in support:
+For example, if the most recent update version available is 2501 (N), the two previous update versions were 2408 and 2406, which means both 2408 (N-1) and 2406 (N-2) remain in support. However, the 2311 (and earlier) version is out of support, as 2311 was N-3 when the 2501 update was released. For the current release of Azure Stack Hub, the following versions are considered in support:
 
+- [Azure Stack Hub 2501](./release-notes.md?view=azs-2501&preserve-view=true)
 - [Azure Stack Hub 2408](./release-notes.md?view=azs-2408&preserve-view=true)
 - [Azure Stack Hub 2406](./release-notes.md?view=azs-2406&preserve-view=true)
-- [Azure Stack Hub 2311](./release-notes.md?view=azs-2311&preserve-view=true)
 
 Microsoft software update packages are non-cumulative and require the previous update package and latest hotfix to be installed as a prerequisite. If you decide to defer one or more updates, consider the overall runtime required to update to the latest version.
 

azure-stack/operator/known-issues.md

@@ -20,11 +20,11 @@ This article lists known issues in Azure Stack Hub releases. The list is updated
 
 To access known issues for a different version, use the version selector dropdown above the table of contents on the left.
 
-::: moniker range=">=azs-2311"
+::: moniker range=">=azs-2406"
 > [!IMPORTANT]  
 > Review this article before applying the update.
 ::: moniker-end
-::: moniker range="<azs-2311"
+::: moniker range="<azs-2406"
 > [!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](azure-stack-servicing-policy.md#keep-your-system-under-support).
 ::: moniker-end
@@ -33,39 +33,20 @@ To access known issues for a different version, use the version selector dropdow
 <!------------------- SUPPORTED VERSIONS ------------------->
 <!---------------------------------------------------------->
 
-::: moniker range="azs-2408"
-## Update
-
-- Applicable: This issue applies to release 2408.
-- Cause: An internal failure of Live Update forces the update method to use FRU instead, which significantly extends the overall update period. Due to this issue, each node update takes an additional 5 hours to complete (approximately).
-- Remediation: If you have more than eight node stamps, you should delay your updates if possible, until a hotfix/inline fix is released.
-- Occurrence: Common.
-
-## Networking
-
-### Outbound ICMP to internet is blocked by default for tenant VM
+::: moniker range="azs-2501"
+<!-- ## Update -->
 
-- Applicable: This issue applies to release 2311 and later.
-- Cause: The issue is caused by a change in the default ICMP behavior introduced with Windows Server 2022 that diverges from previous behavior, as well as Azure behavior.
-- Remediation: You can add an inbound NSG rule to allow outbound ICMP packets to the internet. Microsoft is aware of the issue. 
-- Occurrence: Common.
+<!-- ## Networking -->
 
 ## Compute
 
 ### Azure Kubernetes Service on Azure Stack Hub
 
 - Applicable: This issue applies to release 2311 and later.
-- Cause: Azure Kubernetes Service on Azure Stack Hub, currently in preview, is being discontinued and won't 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.
+- 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.
 
-### A-series VMs deprecated
-
-- Applicable: This issue applies to release 2406 and later.
-- Cause: The A-series VMs are deprecated in Azure, so they shouldn't be used in Azure Stack Hub.
-- Remediation: Although Azure Stack Hub isn't removing the A-series SKU, other undefined behavior might occur if you continue using it (such as with the load balancer, VMSS, etc.). Therefore, you should use a different VM SKU when you're ready. There is no cost difference in using different VM SKUs on Azure Stack Hub.
-- Occurrence: Common.
-
 <!-- ## Alerts -->
 
 <!-- ## Portal -->
@@ -90,10 +71,22 @@ To access known issues for a different version, use the version selector dropdow
 
 ::: moniker-end
 
-::: moniker range="azs-2406"
-<!-- ## Update -->
+::: moniker range="azs-2408"
+## Update
 
-<!-- ## Networking -->
+- Applicable: This issue applies to release 2408.
+- Cause: An internal failure of Live Update forces the update method to use FRU instead, which significantly extends the overall update period. Due to this issue, each node update takes an additional 5 hours to complete (approximately).
+- Remediation: If you have more than eight node stamps, you should delay your updates if possible, until a hotfix/inline fix is released.
+- Occurrence: Common.
+
+## Networking
+
+### Outbound ICMP to internet is blocked by default for tenant VM
+
+- Applicable: This issue applies to release 2311 and later.
+- Cause: The issue is caused by a change in the default ICMP behavior introduced with Windows Server 2022 that diverges from previous behavior, as well as Azure behavior.
+- Remediation: You can add an inbound NSG rule to allow outbound ICMP packets to the internet. Microsoft is aware of the issue. 
+- Occurrence: Common.
 
 ## Compute
 
@@ -104,13 +97,6 @@ To access known issues for a different version, use the version selector dropdow
 - Remediation: Microsoft is aware of the problem and is working on a fix.
 - Occurrence: Common.
 
-### Standard Load Balancer portal error
-
-- Applicable: This issue applies to release 2406 and later.
-- Cause: The Standard Load Balancer portal blades for **Logs** and **Diagnostic settings** both show errors displaying the content.
-- Remediation: The Standard Load Balancer in Azure Stack Hub does not support any diagnostic features.
-- Occurrence: Common.
-
 ### A-series VMs deprecated
 
 - Applicable: This issue applies to release 2406 and later.
@@ -142,7 +128,7 @@ To access known issues for a different version, use the version selector dropdow
 
 ::: moniker-end
 
-::: moniker range="azs-2311"
+::: moniker range="azs-2406"
 <!-- ## Update -->
 
 <!-- ## Networking -->
@@ -156,46 +142,23 @@ To access known issues for a different version, use the version selector dropdow
 - Remediation: Microsoft is aware of the problem and is working on a fix.
 - Occurrence: Common.
 
-### Shutdown using Start-AzsCryptoWipe does not work
-
-- Applicable: This issue applies to release 2311.
-- Cause: In some cases when you run the `Start-AzsCryptoWipe` [command to shut down Azure Stack Hub](/azure-stack/operator/azure-stack-hub-decommission#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.
-
-## Storage
-
-### False storage volume utilization alert in Test-AzureStack report
+### Standard Load Balancer portal error
 
-- 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.
+- Applicable: This issue applies to release 2406 and later.
+- Cause: The Standard Load Balancer portal blades for **Logs** and **Diagnostic settings** both show errors displaying the content.
+- Remediation: The Standard Load Balancer in Azure Stack Hub does not support any diagnostic features.
 - Occurrence: Common.
 
-## Networking
-
-### Outbound ICMP to internet is blocked by default for tenant VM
+### A-series VMs deprecated
 
-- Applicable: This issue applies to release 2311 and later.
-- Cause: The issue is caused by a change in the default ICMP behavior introduced with Windows Server 2022 that diverges from previous behavior, as well as Azure behavior.
-- Remediation: You can add an inbound NSG rule to allow outbound ICMP packets to the internet. Microsoft is aware of the issue. 
+- Applicable: This issue applies to release 2406 and later.
+- Cause: The A-series VMs are deprecated in Azure, so they shouldn't be used in Azure Stack Hub.
+- Remediation: Although Azure Stack Hub isn't removing the A-series SKU, other undefined behavior might occur if you continue using it (such as with the load balancer, VMSS, etc.). Therefore, you should use a different VM SKU when you're ready. There is no cost difference in using different VM SKUs on Azure Stack Hub.
 - Occurrence: Common.
 
 <!-- ## Alerts -->
 
-## Portal
-
-- 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.
-
-### False deployment error in portal for API app deployment
-
-- 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.
+<!-- ## Portal -->
 
 <!-- ## Datacenter integration -->
 
@@ -205,14 +168,7 @@ To access known issues for a different version, use the version selector dropdow
 
 <!-- ## App Service -->
 
-## Resource providers
-
-### Incorrect rotation status after secret rotation of resource provider certificates
-
-- 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.
+<!-- ## Resource providers -->
 
 <!-- ## Usage -->
 
@@ -227,6 +183,9 @@ To access known issues for a different version, use the version selector dropdow
 <!------------------------------------------------------------>
 <!------------------- UNSUPPORTED VERSIONS ------------------->
 <!------------------------------------------------------------>
+::: moniker range="azs-2406"
+## 2406 archived known issues
+::: moniker-end
 ::: moniker range="azs-2311"
 ## 2311 archived known issues
 ::: moniker-end
@@ -303,6 +262,6 @@ To access known issues for a different version, use the version selector dropdow
 ## 1802 archived known issues
 ::: moniker-end
 
-::: moniker range="<azs-2311"
+::: moniker range="<azs-2406"
 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](./relnotearchive/known-issues.md). 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](azure-stack-servicing-policy.md). For further assistance, contact Microsoft Customer Support Services.
 ::: moniker-end