Merge pull request #225986 from LouisBerner/v-lberner-ADO_61978

Updated 2301 release notes with 'Issues fixed' and 'Known issues' sec…

Author: American-Dipper

articles/databox-online/azure-stack-edge-gpu-2301-release-notes.md

@@ -7,7 +7,7 @@ author: alkohli
 ms.service: databox
 ms.subservice: edge
 ms.topic: article
-ms.date: 01/31/2023
+ms.date: 02/03/2023
 ms.author: alkohli
 ---
 
@@ -39,6 +39,24 @@ The 2301 release has the following new features and enhancements:
 - Starting March 2023, Azure Stack Edge devices will be required to be on the 2301 release or later to create a Kubernetes cluster. In preparation for this requirement, it is highly recommended that you update to the latest version as soon as possible.
 - Beginning this release, you can deploy Azure Kubernetes service (AKS) on an Azure Stack Edge cluster. This feature is supported only for SAP and PMEC customers. For more information, see [Deploy AKS on Azure Stack Edge](azure-stack-edge-deploy-aks-on-azure-stack-edge.md).
 
+## Issues fixed in this release
+
+| No. | Feature | Issue |
+| --- | --- | --- |
+|**1.**|Virtual network |In the earlier versions, virtual switches would get deleted when virtual network was deleted, causing the VM provisioning to time out. This issue was fixed and the virtual switch reference is now checked when the virtual network is deleted. |
+|**2.**|Virtual network |In the previous versions, when the VM network interfaces were deleted, IP address was in use even after the associated network interface was removed. In this release, the IP address reference is removed after the VM network interface is deleted. |
+|**3.**|VM |In earlier releases, change notifications weren't cleaned from the datastore. This resulted in the network resource provider (NRP) becoming unresponsive after the datastore was full. This release fixes this issue by adding a notification manager in the NRP to clean up change notifications. | 
+|**4.**|VM |In this release, reliability improvements have been made for the deployment of VM extensions. |
+
+## Known issues in this release
+
+| No. | Feature | Issue | Workaround/comments |
+| --- | --- | --- | --- |
+|**1.**|AKS on Azure Stack Edge |When you update your AKS on Azure Stack Edge deployment from a previous preview version to 2301 release, there is an additional nodepool rollout. |The update may take longer.  |
+|**2.**|Azure portal |When the Arc deployment fails in this release, you will see a generic *NO PARAM* error code, as all the errors are not propagated in the portal. |There is no workaround for this behavior in this release. |
+|**3.**|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 will need to delete the AKS cluster, then modify virtual networks, and then recreate AKS cluster on your Azure Stack Edge. |
+|**4.**|AKS on Azure Stack Edge |In this release, attaching the PVC takes a long time. As a result, some pods that use persistent volumes (PVs) come up slowly after the host reboots. |A workaround is to restart the nodepool VM by connecting via the Windows PowerShell interface of the device. | 
+
 ## Known issues from previous releases
 
 The following table provides a summary of known issues carried over from the previous releases.