Skip to content

Commit 407364b

Browse files
sethmanheimsethmanheim
authored
Merge pull request #17037 from sethmanheim/hubrel2-11
Hub release 2501
2 parents c736f4c + a80bb5c commit 407364b

File tree

5 files changed

+28
-97
lines changed

5 files changed

+28
-97
lines changed

‎azure-local/release-information.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: jasongerend
55
ms.author: jgerend
66
ms.topic: conceptual
77
ms.service: azure-local
8-
ms.date: 01/13/2025
8+
ms.date: 02/10/2025
99
---
1010

1111
# Azure Stack HCI, version 22H2 release information
@@ -26,6 +26,7 @@ All dates are listed in ISO 8601 format: *YYYY-MM-DD*
2626

2727
| **OS build** | **Availability date** | **KB article** |
2828
|:-|:-|:-|
29+
| 20349.3207 | 2025-02-11 | [KB 5051979](https://support.microsoft.com/en-us/topic/3ed79598-31b4-43b5-b422-758d074b8331) |
2930
| 20349.3091 | 2025-01-14 | [KB 5049983](https://support.microsoft.com/topic/916b5502-9602-4ed0-a0ee-c7a3c7ebcfd6) |
3031
| 20349.2966 | 2024-12-10 | [KB 5048654](https://support.microsoft.com/topic/7a18b155-a0ed-4b39-8968-262c30590a2e) |
3132
| 20349.2849 | 2024-11-12 | [KB 5046616](https://support.microsoft.com/topic/49a4f881-4e4d-4024-a43f-365cb392df29) |

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ titleSuffix: Azure Stack Hub
44
description: Learn about the Azure Stack Hub servicing policy and how to keep an integrated system in a supported state.
55
author: sethmanheim
66
ms.topic: article
7-
ms.date: 11/25/2024
7+
ms.date: 02/11/2025
88
ms.author: sethm
99
ms.lastreviewed: 03/18/2020
1010

‎azure-stack/operator/known-issues.md

Lines changed: 4 additions & 93 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Azure Stack Hub known issues
33
description: Learn about known issues in Azure Stack Hub releases.
44
author: sethmanheim
55
ms.topic: article
6-
ms.date: 01/08/2025
6+
ms.date: 02/11/2025
77
ms.author: sethm
88
ms.reviewer: rtiberiu
99
ms.lastreviewed: 11/30/2023
@@ -212,98 +212,6 @@ To access known issues for a different version, use the version selector dropdow
212212

213213
::: moniker-end
214214

215-
::: moniker range="azs-2311"
216-
217-
<!-- ## Update -->
218-
219-
<!-- ## Networking -->
220-
221-
## Compute
222-
223-
### Azure Kubernetes Service on Azure Stack Hub
224-
225-
- Applicable: This issue applies to release 2311 and later.
226-
- 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.
227-
- Remediation: Microsoft is aware of the problem and is working on a fix.
228-
- Occurrence: Common.
229-
230-
### Shutdown using Start-AzsCryptoWipe does not work
231-
232-
- Applicable: This issue applies to release 2311.
233-
- 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.
234-
- Remediation: If you see that any physical machine is not powered down, you must turn off that machine through the Baseboard Management Controller (BMC).
235-
- Occurrence: Common.
236-
237-
## Storage
238-
239-
### False storage volume utilization alert in Test-AzureStack report
240-
241-
- Applicable: This issue applies to release 2311 and later.
242-
- 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.
243-
- Remediation: You can ignore the alert in the Test-AzureStack report. Microsoft is aware of the issue and is working on a fix.
244-
- Occurrence: Common.
245-
246-
## Networking
247-
248-
### Outbound ICMP to internet is blocked by default for tenant VM
249-
250-
- Applicable: This issue applies to release 2311 and later.
251-
- 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.
252-
- Remediation: You can add an inbound NSG rule to allow outbound ICMP packets to the internet. Microsoft is aware of the issue.
253-
- Occurrence: Common.
254-
255-
<!-- ## Alerts -->
256-
257-
## Portal
258-
259-
### Can't use Flow Timeout and BGP community string DNS options in the portal
260-
261-
- Applicable: This issue applies to release 2311.
262-
- 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.
263-
- Remediation: Microsoft is aware of the problem and is working on a fix.
264-
- Occurrence: Common.
265-
266-
### False deployment error in portal for API app deployment
267-
268-
- Applicable: This issue applies to release 2311 and later.
269-
- 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.
270-
- Remediation: Check your API app after deployment to ensure deployment was successful. Microsoft is aware of the problem and is working on a fix.
271-
- Occurrence: Common.
272-
273-
### Nodes blade fails to load
274-
275-
- Applicable: This issue applies to release 2311 and later.
276-
- Cause: The **Nodes** blade on the portal fails to load when a GPU property isn't configured.
277-
- Remediation: Microsoft is aware of the issue and is working on a fix.
278-
- Occurrence: Occasional.
279-
280-
<!-- ## Datacenter integration -->
281-
282-
<!-- ## Storage -->
283-
284-
<!-- ## SQL and MySQL-->
285-
286-
<!-- ## App Service -->
287-
288-
## Resource providers
289-
290-
### Incorrect rotation status after secret rotation of resource provider certificates
291-
292-
- Applicable: This issue applies to all Azure Stack Hub add-on resource providers.
293-
- 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.
294-
- Remediation: None. No impact to your system or workloads.
295-
- Occurrence: All supported versions of Azure Stack Hub.
296-
297-
<!-- ## Usage -->
298-
299-
<!-- ### Identity -->
300-
301-
<!-- ### Marketplace -->
302-
303-
<!-- ## Event Hubs -->
304-
305-
::: moniker-end
306-
307215
::: moniker range="azs-2406 || azs-2408 || azs-2311"
308216
## Update
309217

@@ -318,6 +226,9 @@ To access known issues for a different version, use the version selector dropdow
318226
<!------------------------------------------------------------>
319227
<!------------------- UNSUPPORTED VERSIONS ------------------->
320228
<!------------------------------------------------------------>
229+
::: moniker range="azs-2311"
230+
## 2311 archived known issues
231+
::: moniker-end
321232
::: moniker range="azs-2306"
322233
## 2306 archived known issues
323234
::: moniker-end

‎azure-stack/operator/release-notes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Azure Stack Hub release notes
33
description: Release notes for Azure Stack Hub integrated systems, including updates and bug fixes.
44
author: sethmanheim
55
ms.topic: article
6-
ms.date: 02/08/2025
6+
ms.date: 02/11/2025
77
ms.author: sethm
88
ms.reviewer: rtiberiu
99
ms.lastreviewed: 04/22/2024

‎azure-stack/operator/relnotearchive/known-issues.md

Lines changed: 20 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,7 @@ To access known issues for a different archived version, use the version selecto
2222
<!---------------------------------------------------------->
2323

2424
::: moniker range="azs-2311"
25+
2526
<!-- ## Update -->
2627

2728
<!-- ## Networking -->
@@ -31,7 +32,7 @@ To access known issues for a different archived version, use the version selecto
3132
### Azure Kubernetes Service on Azure Stack Hub
3233

3334
- Applicable: This issue applies to release 2311 and later.
34-
- 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.
35+
- 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.
3536
- Remediation: Microsoft is aware of the problem and is working on a fix.
3637
- Occurrence: Common.
3738

@@ -51,10 +52,21 @@ To access known issues for a different archived version, use the version selecto
5152
- Remediation: You can ignore the alert in the Test-AzureStack report. Microsoft is aware of the issue and is working on a fix.
5253
- Occurrence: Common.
5354

55+
## Networking
56+
57+
### Outbound ICMP to internet is blocked by default for tenant VM
58+
59+
- Applicable: This issue applies to release 2311 and later.
60+
- 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.
61+
- Remediation: You can add an inbound NSG rule to allow outbound ICMP packets to the internet. Microsoft is aware of the issue.
62+
- Occurrence: Common.
63+
5464
<!-- ## Alerts -->
5565

5666
## Portal
5767

68+
### Can't use Flow Timeout and BGP community string DNS options in the portal
69+
5870
- Applicable: This issue applies to release 2311.
5971
- 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.
6072
- Remediation: Microsoft is aware of the problem and is working on a fix.
@@ -67,6 +79,13 @@ To access known issues for a different archived version, use the version selecto
6779
- Remediation: Check your API app after deployment to ensure deployment was successful. Microsoft is aware of the problem and is working on a fix.
6880
- Occurrence: Common.
6981

82+
### Nodes blade fails to load
83+
84+
- Applicable: This issue applies to release 2311 and later.
85+
- Cause: The **Nodes** blade on the portal fails to load when a GPU property isn't configured.
86+
- Remediation: Microsoft is aware of the issue and is working on a fix.
87+
- Occurrence: Occasional.
88+
7089
<!-- ## Datacenter integration -->
7190

7291
<!-- ## Storage -->

0 commit comments

Comments
 (0)