Skip to content

Commit 67cb5a2

Browse files
sethmanheimsethmanheim
authored
Merge pull request #17047 from MicrosoftDocs/release-ash-2501
Merge release-ash-2501 for Hub release
2 parents 3df4177 + 87b3bfb commit 67cb5a2

File tree

6 files changed

+134
-196
lines changed

6 files changed

+134
-196
lines changed

‎azure-stack/operator/TOC.yml

Lines changed: 2 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -32,20 +32,10 @@
3232
href: hotfix-1-2406-1-15.md
3333
- name: Hotfix 1.2406.1.14
3434
href: hotfix-1-2406-1-14.md
35-
- name: 2311
36-
items:
37-
- name: Hotfix 1.2311.3.62
38-
href: hotfix-1-2311-3-62.md
39-
- name: Hotfix 1.2311.3.61
40-
href: hotfix-1-2311-3-61.md
41-
- name: Hotfix 1.2311.3.50
42-
href: hotfix-1-2311-3-50.md
43-
- name: Hotfix 1.2311.3.44
44-
href: hotfix-1-2311-3-44.md
45-
- name: Hotfix 1.2311.2.23
46-
href: hotfix-1-2311-2-23.md
4735
- name: Archive
4836
items:
37+
- name: Hotfix 1.2311.3.62
38+
href: hotfix-1-2311-3-62.md
4939
- name: Hotfix 1.2306.4.102
5040
href: hotfix-1-2306-4-102.md
5141
- name: Hotfix 1.2301.3.97

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

Lines changed: 4 additions & 4 deletions
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: 10/24/2024
7+
ms.date: 02/11/2025
88
ms.author: sethm
99
ms.lastreviewed: 03/18/2020
1010

@@ -46,9 +46,9 @@ Find documentation on how to plan for and manage updates, and how to determine y
4646

4747
For information about a specific update, including how to download it, see the release notes for that update:
4848

49+
- [Azure Stack Hub 2501 update](./release-notes.md?view=azs-2501&preserve-view=true)
4950
- [Azure Stack Hub 2408 update](./release-notes.md?view=azs-2408&preserve-view=true)
5051
- [Azure Stack Hub 2406 update](./release-notes.md?view=azs-2406&preserve-view=true)
51-
- [Azure Stack Hub 2311 update](./release-notes.md?view=azs-2311&preserve-view=true)
5252

5353
## Hotfixes
5454

@@ -78,11 +78,11 @@ You must also have an active support agreement with the hardware partner that ma
7878

7979
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.
8080

81-
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:
81+
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:
8282

83+
- [Azure Stack Hub 2501](./release-notes.md?view=azs-2501&preserve-view=true)
8384
- [Azure Stack Hub 2408](./release-notes.md?view=azs-2408&preserve-view=true)
8485
- [Azure Stack Hub 2406](./release-notes.md?view=azs-2406&preserve-view=true)
85-
- [Azure Stack Hub 2311](./release-notes.md?view=azs-2311&preserve-view=true)
8686

8787
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.
8888

‎azure-stack/operator/hotfix-1-2311-3-62.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,19 +3,16 @@ title: Azure Stack Hub hotfix 1.2311.3.62
33
description: Summary of Azure Stack Hub hotfix 1.2311.3.62
44
author: sethmanheim
55
ms.topic: article
6-
ms.date: 01/08/2025
6+
ms.date: 02/12/2025
77
ms.author: sethm
88
ms.lastreviewed: 09/24/2024
99
---
1010

1111
# Azure Stack Hub hotfix 1.2311.3.62
1212

13-
## Summary
13+
## Summary of fixes
1414

1515
- Fixed an issue with DNS zone creation in SQL and MySQL resource providers.
16-
17-
## Fixes rolled up from previous hotfix releases
18-
1916
- Fixed bugs causing infrastructure faults.
2017
- Fixed an issue in which users were able to create duplicate and external infrastructure DNS zones.
2118
- Fixed the **CloudManifest** feature to avoid adding non-self-signed certificates to the root store.

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

Lines changed: 52 additions & 96 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
@@ -20,11 +20,11 @@ This article lists known issues in Azure Stack Hub releases. The list is updated
2020

2121
To access known issues for a different version, use the version selector dropdown above the table of contents on the left.
2222

23-
::: moniker range=">=azs-2311"
23+
::: moniker range=">=azs-2406"
2424
> [!IMPORTANT]
2525
> Review this article before applying the update.
2626
::: moniker-end
27-
::: moniker range="<azs-2311"
27+
::: moniker range="<azs-2406"
2828
> [!IMPORTANT]
2929
> 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).
3030
::: moniker-end
@@ -36,58 +36,30 @@ To access known issues for a different version, use the version selector dropdow
3636
<!------------------- SUPPORTED VERSIONS ------------------->
3737
<!---------------------------------------------------------->
3838

39-
::: moniker range="azs-2408"
39+
::: moniker range="azs-2501"
4040
<!-- ## Update -->
4141

42-
## Networking
43-
44-
### Outbound ICMP to internet is blocked by default for tenant VM
45-
46-
- Applicable: This issue applies to release 2311 and later.
47-
- 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.
48-
- Remediation: You can add an inbound NSG rule to allow outbound ICMP packets to the internet. Microsoft is aware of the issue.
49-
- Occurrence: Common.
42+
<!-- ## Networking -->
5043

5144
## Compute
5245

5346
### Azure Kubernetes Service on Azure Stack Hub
5447

5548
- Applicable: This issue applies to release 2311 and later.
5649
- 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.
57-
- Remediation: Microsoft is aware of the issue and is working on a fix.
58-
- Occurrence: Common.
59-
60-
### A-series VMs deprecated
61-
62-
- Applicable: This issue applies to release 2406 and later.
63-
- Cause: The A-series VMs are deprecated in Azure, so they shouldn't be used in Azure Stack Hub.
64-
- 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.
50+
- Remediation: Microsoft is aware of the problem and is working on a fix.
6551
- Occurrence: Common.
6652

67-
### ESv3 and DSv3 series don't have nested virtualization enabled
53+
### Graph API retirement
6854

69-
- Applicable: This issue applies to release 2408.
70-
- Cause: Neither of the [newly introduced ESv3 or DSv3 series](../user/azure-stack-vm-sizes.md#esv3-series); for example, E20s_v3, has nested virtualization enabled.
71-
- Remediation: Microsoft is aware of the issue and is working on a fix.
72-
- Occurrence: Common.
55+
- Applicable: This issue applies to all supported versions of Azure Stack Hub.
56+
- Cause: The Microsoft Entra ID [Graph API service is being retired](https://techcommunity.microsoft.com/blog/microsoft-entra-blog/important-update-azure-ad-graph-api-retirement/4090534).
57+
- Remediation: Run the [script included in this article](graph-api-retirement.md) for all impacted applications. The script sets a flag that configures these applications for an extension that allows these specific applications to continue calling the legacy Graph API until June 2025.
58+
- Occurrence: Occasional.
7359

7460
<!-- ## Alerts -->
7561

76-
## Portal
77-
78-
### Deployments blade under subscription fails to load
79-
80-
- Applicable: This issue applies to release 2406 and later.
81-
- Cause: Due to a change in how subscription-level deployments are stored, an internal server error occurs when deploying or viewing deployments at subscription scope.
82-
- Remediation: Microsoft is aware of the issue and is working on a fix.
83-
- Occurrence: Common.
84-
85-
### Nodes blade fails to load
86-
87-
- Applicable: This issue applies to release 2311 and later.
88-
- Cause: The **Nodes** blade on the portal fails to load when a GPU property isn't configured.
89-
- Remediation: Microsoft is aware of the issue and is working on a fix.
90-
- Occurrence: Occasional.
62+
<!-- ## Portal -->
9163

9264
<!-- ## Datacenter integration -->
9365

@@ -109,24 +81,25 @@ To access known issues for a different version, use the version selector dropdow
10981

11082
::: moniker-end
11183

112-
::: moniker range="azs-2406"
113-
84+
::: moniker range="azs-2408"
11485
<!-- ## Update -->
11586

116-
## Compute
87+
## Networking
11788

118-
### Azure Kubernetes Service on Azure Stack Hub
89+
### Outbound ICMP to internet is blocked by default for tenant VM
11990

12091
- Applicable: This issue applies to release 2311 and later.
121-
- 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.
122-
- Remediation: Microsoft is aware of the problem and is working on a fix.
92+
- 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.
93+
- Remediation: You can add an inbound NSG rule to allow outbound ICMP packets to the internet. Microsoft is aware of the issue.
12394
- Occurrence: Common.
12495

125-
### Standard Load Balancer portal error
96+
## Compute
12697

127-
- Applicable: This issue applies to release 2406 and later.
128-
- Cause: The Standard Load Balancer portal blades for **Logs** and **Diagnostic settings** both show errors displaying the content.
129-
- Remediation: The Standard Load Balancer in Azure Stack Hub does not support any diagnostic features.
98+
### Azure Kubernetes Service on Azure Stack Hub
99+
100+
- Applicable: This issue applies to release 2311 and later.
101+
- 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.
102+
- Remediation: Microsoft is aware of the issue and is working on a fix.
130103
- Occurrence: Common.
131104

132105
### A-series VMs deprecated
@@ -136,6 +109,15 @@ To access known issues for a different version, use the version selector dropdow
136109
- 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.
137110
- Occurrence: Common.
138111

112+
### ESv3 and DSv3 series don't have nested virtualization enabled
113+
114+
- Applicable: This issue applies to release 2408.
115+
- Cause: Neither of the [newly introduced ESv3 or DSv3 series](../user/azure-stack-vm-sizes.md#esv3-series); for example, E20s_v3, has nested virtualization enabled.
116+
- Remediation: Microsoft is aware of the issue and is working on a fix.
117+
- Occurrence: Common.
118+
119+
<!-- ## Alerts -->
120+
139121
## Portal
140122

141123
### Deployments blade under subscription fails to load
@@ -152,8 +134,6 @@ To access known issues for a different version, use the version selector dropdow
152134
- Remediation: Microsoft is aware of the issue and is working on a fix.
153135
- Occurrence: Occasional.
154136

155-
<!-- ## Alerts -->
156-
157137
<!-- ## Datacenter integration -->
158138

159139
<!-- ## Storage -->
@@ -174,12 +154,10 @@ To access known issues for a different version, use the version selector dropdow
174154

175155
::: moniker-end
176156

177-
::: moniker range="azs-2311"
157+
::: moniker range="azs-2406"
178158

179159
<!-- ## Update -->
180160

181-
<!-- ## Networking -->
182-
183161
## Compute
184162

185163
### Azure Kubernetes Service on Azure Stack Hub
@@ -189,47 +167,27 @@ To access known issues for a different version, use the version selector dropdow
189167
- Remediation: Microsoft is aware of the problem and is working on a fix.
190168
- Occurrence: Common.
191169

192-
### Shutdown using Start-AzsCryptoWipe does not work
193-
194-
- Applicable: This issue applies to release 2311.
195-
- 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.
196-
- Remediation: If you see that any physical machine is not powered down, you must turn off that machine through the Baseboard Management Controller (BMC).
197-
- Occurrence: Common.
198-
199-
## Storage
200-
201-
### False storage volume utilization alert in Test-AzureStack report
170+
### Standard Load Balancer portal error
202171

203-
- Applicable: This issue applies to release 2311 and later.
204-
- 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.
205-
- Remediation: You can ignore the alert in the Test-AzureStack report. Microsoft is aware of the issue and is working on a fix.
172+
- Applicable: This issue applies to release 2406 and later.
173+
- Cause: The Standard Load Balancer portal blades for **Logs** and **Diagnostic settings** both show errors displaying the content.
174+
- Remediation: The Standard Load Balancer in Azure Stack Hub does not support any diagnostic features.
206175
- Occurrence: Common.
207176

208-
## Networking
209-
210-
### Outbound ICMP to internet is blocked by default for tenant VM
177+
### A-series VMs deprecated
211178

212-
- Applicable: This issue applies to release 2311 and later.
213-
- 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.
214-
- Remediation: You can add an inbound NSG rule to allow outbound ICMP packets to the internet. Microsoft is aware of the issue.
179+
- Applicable: This issue applies to release 2406 and later.
180+
- Cause: The A-series VMs are deprecated in Azure, so they shouldn't be used in Azure Stack Hub.
181+
- 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.
215182
- Occurrence: Common.
216183

217-
<!-- ## Alerts -->
218-
219184
## Portal
220185

221-
### Can't use Flow Timeout and BGP community string DNS options in the portal
222-
223-
- Applicable: This issue applies to release 2311.
224-
- 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.
225-
- Remediation: Microsoft is aware of the problem and is working on a fix.
226-
- Occurrence: Common.
227-
228-
### False deployment error in portal for API app deployment
186+
### Deployments blade under subscription fails to load
229187

230-
- Applicable: This issue applies to release 2311 and later.
231-
- 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.
232-
- Remediation: Check your API app after deployment to ensure deployment was successful. Microsoft is aware of the problem and is working on a fix.
188+
- Applicable: This issue applies to release 2406 and later.
189+
- Cause: Due to a change in how subscription-level deployments are stored, an internal server error occurs when deploying or viewing deployments at subscription scope.
190+
- Remediation: Microsoft is aware of the issue and is working on a fix.
233191
- Occurrence: Common.
234192

235193
### Nodes blade fails to load
@@ -239,6 +197,8 @@ To access known issues for a different version, use the version selector dropdow
239197
- Remediation: Microsoft is aware of the issue and is working on a fix.
240198
- Occurrence: Occasional.
241199

200+
<!-- ## Alerts -->
201+
242202
<!-- ## Datacenter integration -->
243203

244204
<!-- ## Storage -->
@@ -247,14 +207,7 @@ To access known issues for a different version, use the version selector dropdow
247207

248208
<!-- ## App Service -->
249209

250-
## Resource providers
251-
252-
### Incorrect rotation status after secret rotation of resource provider certificates
253-
254-
- Applicable: This issue applies to all Azure Stack Hub add-on resource providers.
255-
- 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.
256-
- Remediation: None. No impact to your system or workloads.
257-
- Occurrence: All supported versions of Azure Stack Hub.
210+
<!-- ## Resource providers -->
258211

259212
<!-- ## Usage -->
260213

@@ -280,6 +233,9 @@ To access known issues for a different version, use the version selector dropdow
280233
<!------------------------------------------------------------>
281234
<!------------------- UNSUPPORTED VERSIONS ------------------->
282235
<!------------------------------------------------------------>
236+
::: moniker range="azs-2311"
237+
## 2311 archived known issues
238+
::: moniker-end
283239
::: moniker range="azs-2306"
284240
## 2306 archived known issues
285241
::: moniker-end
@@ -356,6 +312,6 @@ To access known issues for a different version, use the version selector dropdow
356312
## 1802 archived known issues
357313
::: moniker-end
358314

359-
::: moniker range="<azs-2311"
315+
::: moniker range="<azs-2406"
360316
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.
361317
::: moniker-end

0 commit comments

Comments
 (0)