You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/databox-online/azure-stack-edge-gpu-2407-release-notes.md
+23-35Lines changed: 23 additions & 35 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ author: alkohli
7
7
ms.service: databox
8
8
ms.subservice: edge
9
9
ms.topic: article
10
-
ms.date: 08/07/2024
10
+
ms.date: 08/14/2024
11
11
ms.author: alkohli
12
12
---
13
13
@@ -19,7 +19,7 @@ The following release notes identify critical open issues and resolved issues fo
19
19
20
20
The release notes are continuously updated, and as critical issues requiring a workaround are discovered, they're added. Before you deploy your device, carefully review the information contained in the release notes.
21
21
22
-
This article applies to the **Azure Stack Edge 2407** release, which maps to software version **3.2.2642.2487**.
22
+
This article applies to the **Azure Stack Edge 2407** release, which maps to software version **3.2.2754.1029**.
23
23
24
24
> [!Warning]
25
25
> In this release, you must update the packet core version to AP5GC 2308 before you update to Azure Stack Edge 2407. For detailed steps, see [Azure Private 5G Core 2308 release notes](../private-5g-core/azure-private-5g-core-release-notes-2308.md).
@@ -28,61 +28,46 @@ This article applies to the **Azure Stack Edge 2407** release, which maps to sof
28
28
29
29
## Supported update paths
30
30
31
-
To apply the 2403 update, your device must be running version 2303 or later.
31
+
To apply the 2407 update, your device must be running version 2303 or later.
32
32
33
33
- If you aren't running the minimum required version, you see this error:
34
34
35
35
*Update package can't be installed as its dependencies aren't met.*
36
36
37
-
- You can update to 2303 from 2207 or later, and then update to 2403.
37
+
- You can update to 2303 from 2207 or later, and then update to 2407.
38
38
39
39
You can update to the latest version using the following update paths:
40
40
41
-
| Current version of Azure Stack Edge software and Kubernetes | Update to Azure Stack Edge software and Kubernetes | Desired update to 2403|
41
+
| Current version of Azure Stack Edge software and Kubernetes | Update to Azure Stack Edge software and Kubernetes | Desired update to 2407|
42
42
| --------------------| -----------| -----------|
43
-
|2207 |2303 |2403|
44
-
|2209 |2303 |2403|
45
-
|2210 |2303 |2403|
46
-
|2301 |2303 |2403|
47
-
|2303 |Directly to |2403|
43
+
|2207 |2303 |2407|
44
+
|2209 |2303 |2407|
45
+
|2210 |2303 |2407|
46
+
|2301 |2303 |2407|
47
+
|2303 |Directly to |2407|
48
48
49
49
## What's new
50
50
51
-
The 2403 release has the following new features and enhancements:
51
+
The 2407 release has the following new features and enhancements:
52
52
53
-
- Deprecated support for Azure Kubernetes service telemetry on Azure Stack Edge.
54
-
- Zone-label support for two-node Kubernetes clusters.
55
-
- Hyper-V VM management, memory usage monitoring on Azure Stack Edge host.
53
+
- Deprecated support for Ubuntu 18.04 LTS GPU extension. The GPU extension is no longer supported on Ubuntu 18.04 GPU VMs running on Azure Stack Edge devices. If you plan to utilize the Ubuntu version 18.04 LTS distro, see steps for manual GPU driver installation at [CUDA Toolkit 12.1 Update 1 Downloads](https://developer.nvidia.com/cuda-12-1-1-download-archive?target_os=Linux&target_arch=x86_64&Distribution=Ubuntu&target_version=18.04&target_type=deb_local).
56
54
57
-
## Issues fixed in this release
55
+
You may need to download the CUDA signing key before the installation.
56
+
57
+
For detailed steps to install the signing key, see [Troubleshoot GPU extension issues for GPU VMs on Azure Stack Edge Pro GPU](azure-stack-edge-gpu-troubleshoot-virtual-machine-gpu-extension-installation.md#in-versions-lower-than-2205-linux-gpu-extension-installs-old-signing-keys-signature-andor-required-key-missing).
58
58
59
+
<!--!## Issues fixed in this release
60
+
==previous==
59
61
| No. | Feature | Issue |
60
62
| --- | --- | --- |
61
-
|**1.**| Clustering | Two-node cold boot of the server causes high availability VM cluster resources to come up as offline. Changed ColdStartSetting to AlwaysStart. |
62
-
|**2.**| Marketplace image support | Fixed bug allowing Windows Marketplace image on Azure Stack Edge A and TMA. |
63
-
|**3.**| Network connectivity | Fixed VM NIC link flapping after Azure Stack Edge host power off/on, which can cause VM losing its DHCP IP. |
64
-
|**4.**| Network connectivity |Due to proxy ARP configurations in some customer environments, **IP address in use** check returns false positive even though no endpoint in the network is using the IP. The fix skips the ARP-based VM **IP address in use** check if the IP address is allocated from an internal network managed by Azure Stack Edge. |
65
-
|**5.**| Network connectivity | VM NIC change operation times out after 3 hours, which blocks other VM update operations. On Microsoft Kubernetes clusters, Persistent Volume (PV) dependent pods get stuck. The issue occurs when multiple NICs within a VM are being transferred from a VLAN virtual network to a non-VLAN virtual network. After the fix, the VM NIC change operation times out quickly and the VM update won't be blocked. |
66
-
|**6.**| Kubernetes | Overall two-node Kubernetes resiliency improvements, like increasing memory for control plane for AKS workload cluster, increasing limits for etcd, multi-replica, and hard anti-affinity support for core DNS and Azure disk csi controller pods and improve VM failover times. |
67
-
|**7.**| Compute Diagnostic and Update | Resiliency fixes |
68
-
|**8.**| Security | STIG security fixes for Mariner Guest OS for Azure Kubernetes service on Azure Stack Edge. |
69
-
|**9.**| VM operations | On an Azure Stack Edge cluster that deploys an AP5GC workload, after a host power cycle test, when the host returns a transient error about CPU group configuration, AzSHostAgent would crash. This caused a VM operations failure. The fix made *AzSHostAgent* resilient to a transient CPU group error. |
70
-
71
-
<!--!## Known issues in this release
72
-
73
-
| No. | Feature | Issue | Workaround/comments |
74
-
| --- | --- | --- | --- |
75
-
|**1.**|AKS... |The AKS Kubernetes... |
76
-
|**2.**|Wi-Fi... |Starting this release... | |-->
63
+
|**1.**| Clustering |-->
77
64
78
65
## Known issues in this release
79
66
80
67
| No. | Feature | Issue | Workaround/comments |
81
68
| --- | --- | --- | --- |
82
-
|**1.**| Azure Storage Explorer | The Blob storage endpoint certificate that's autogenerated by the Azure Stack Edge device might not work properly with Azure Storage Explorer. | Replace the Blob storage endpoint certificate. For detailed steps, see [Bring your own certificates](azure-stack-edge-gpu-deploy-configure-certificates.md#bring-your-own-certificates). |
83
-
|**2.**| Network connectivity | On a two-node Azure Stack Edge Pro 2 cluster with a teamed virtual switch for Port 1 and Port 2, if a Port 1 or Port 2 link is down, it can take up to 5 seconds to resume network connectivity on the remaining active port. If a Kubernetes cluster uses this teamed virtual switch for management traffic, pod communication may be disrupted up to 5 seconds. ||
84
-
|**3.**| Virtual machine | After the host or Kubernetes node pool VM is shut down, there's a chance that kubelet in node pool VM fails to start due to a CPU static policy error. Node pool VM shows **Not ready** status, and pods won't be scheduled on this VM. | Enter a support session and ssh into the node pool VM, then follow steps in [Changing the CPU Manager Policy](https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/#changing-the-cpu-manager-policy) to remediate the kubelet service. |
85
-
69
+
|**1.**|VM creation | Image directory is still the old location causing VM creation failure on Azure Stack Edge 2403. ||
70
+
86
71
## Known issues from previous releases
87
72
88
73
The following table provides a summary of known issues carried over from the previous releases.
@@ -118,6 +103,9 @@ The following table provides a summary of known issues carried over from the pre
118
103
|**27.**|AKS on Azure Stack Edge |In this release, you can't modify the virtual networks once the AKS cluster is deployed on your Azure Stack Edge cluster.| To modify the virtual network, you must delete the AKS cluster, then modify virtual networks, and then recreate AKS cluster on your Azure Stack Edge. |
119
104
|**28.**|AKS Update |The AKS Kubernetes update might fail if one of the AKS VMs isn't running. This issue might be seen in the two-node cluster. |If the AKS update has failed, [Connect to the PowerShell interface of the device](azure-stack-edge-gpu-connect-powershell-interface.md). Check the state of the Kubernetes VMs by running `Get-VM` cmdlet. If the VM is off, run the `Start-VM` cmdlet to restart the VM. Once the Kubernetes VM is running, reapply the update. |
120
105
|**29.**|Wi-Fi |Wi-Fi functionality for Azure Stack Edge Mini R is deprecated. ||
106
+
|**1.**| Azure Storage Explorer | The Blob storage endpoint certificate that's autogenerated by the Azure Stack Edge device might not work properly with Azure Storage Explorer. | Replace the Blob storage endpoint certificate. For detailed steps, see [Bring your own certificates](azure-stack-edge-gpu-deploy-configure-certificates.md#bring-your-own-certificates). |
107
+
|**2.**| Network connectivity | On a two-node Azure Stack Edge Pro 2 cluster with a teamed virtual switch for Port 1 and Port 2, if a Port 1 or Port 2 link is down, it can take up to 5 seconds to resume network connectivity on the remaining active port. If a Kubernetes cluster uses this teamed virtual switch for management traffic, pod communication may be disrupted up to 5 seconds. ||
108
+
|**3.**| Virtual machine | After the host or Kubernetes node pool VM is shut down, there's a chance that kubelet in node pool VM fails to start due to a CPU static policy error. Node pool VM shows **Not ready** status, and pods won't be scheduled on this VM. | Enter a support session and ssh into the node pool VM, then follow steps in [Changing the CPU Manager Policy](https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/#changing-the-cpu-manager-policy) to remediate the kubelet service. |
- Device Kubernetes workload profile: Other workloads.
33
+
- Kubernetes server version: v1.28.5.
34
34
- IoT Edge version: 0.1.0-beta15.
35
-
- Azure Arc version: 1.14.5.
36
-
- GPU driver version: 535.104.05.
35
+
- Azure Arc version: 1.16.10.
36
+
- GPU driver version: 535.161.08.
37
37
- CUDA version: 12.2.
38
38
39
-
For information on what's new in this update, go to [Release notes](azure-stack-edge-gpu-2403-release-notes.md).
39
+
For information on what's new in this update, go to [Release notes](azure-stack-edge-gpu-2407-release-notes.md).
40
40
41
-
**To apply the 2403 update, your device must be running version 2203 or later.**
41
+
**To apply the 2407 update, your device must be running version 2203 or later.**
42
42
43
43
- If you aren't running the minimum required version, you see this error:
44
44
45
45
*Update package can't be installed as its dependencies aren't met.*
46
46
47
-
- You can update to 2303 from 2207 or later, and then install 2403.
47
+
- You can update to 2303 from 2207 or later, and then install 2407.
48
48
49
49
Supported update paths:
50
50
51
-
| Current version of Azure Stack Edge software and Kubernetes | Upgrade to Azure Stack Edge software and Kubernetes | Desired update to 2403|
51
+
| Current version of Azure Stack Edge software and Kubernetes | Upgrade to Azure Stack Edge software and Kubernetes | Desired update to 2407|
52
52
|-------|----------|------------ |
53
-
| 2207 | 2303 |2403|
54
-
| 2209 | 2303 |2403|
55
-
| 2210 | 2303 |2403|
56
-
| 2301 | 2303 |2403|
57
-
| 2303 | Directly to |2403|
53
+
| 2207 | 2303 |2407|
54
+
| 2209 | 2303 |2407|
55
+
| 2210 | 2303 |2407|
56
+
| 2301 | 2303 |2407|
57
+
| 2303 | Directly to |2407|
58
58
59
59
### Update Azure Kubernetes service on Azure Stack Edge
60
60
61
61
> [!IMPORTANT]
62
62
> Use the following procedure only if you are an SAP or a PMEC customer.
63
63
64
-
If you have Azure Kubernetes service deployed and your Azure Stack Edge device and Kubernetes versions are either 2207 or 2209, you must update in multiple steps to apply 2403.
64
+
If you have Azure Kubernetes service deployed and your Azure Stack Edge device and Kubernetes versions are either 2207 or 2209, you must update in multiple steps to apply 2407.
65
65
66
-
Use the following steps to update your Azure Stack Edge version and Kubernetes version to 2403:
66
+
Use the following steps to update your Azure Stack Edge version and Kubernetes version to 2407:
67
67
68
68
1. Update your device version to 2303.
69
69
1. Update your Kubernetes version to 2210.
70
70
1. Update your Kubernetes version to 2303.
71
-
1. Update both device software and Kubernetes to 2403.
71
+
1. Update both device software and Kubernetes to 2407.
72
72
73
-
If you're running 2210 or 2301, you can update both your device version and Kubernetes version directly to 2303 and then to 2403.
73
+
If you're running 2210 or 2301, you can update both your device version and Kubernetes version directly to 2303 and then to 2407.
74
74
75
-
If you're running 2303, you can update both your device version and Kubernetes version directly to 2403.
75
+
If you're running 2303, you can update both your device version and Kubernetes version directly to 2407.
76
76
77
-
In Azure portal, the process requires two clicks, the first update gets your device version to 2303 and your Kubernetes version to 2210, and the second update gets your Kubernetes version upgraded to 2403.
77
+
In Azure portal, the process requires two clicks, the first update gets your device version to 2303 and your Kubernetes version to 2210, and the second update gets your Kubernetes version upgraded to 2407.
78
78
79
-
From the local UI, you'll have to run each update separately: update the device version to 2303, update Kubernetes version to 2210, update Kubernetes version to 2303, and then the third update gets both the device version and Kubernetes version to 2403.
79
+
From the local UI, you'll have to run each update separately: update the device version to 2303, update Kubernetes version to 2210, update Kubernetes version to 2303, and then the third update gets both the device version and Kubernetes version to 2407.
80
80
81
81
Each time you change the Kubernetes profile, you're prompted for the Kubernetes update. Go ahead and apply the update.
0 commit comments