Azure Stack Edge 2210 release notes

APPLIES TO: Yes for Pro GPU SKUAzure Stack Edge Pro - GPUYes for Pro 2 SKUAzure Stack Edge Pro 2Yes for Pro R SKUAzure Stack Edge Pro RYes for Mini R SKUAzure Stack Edge Mini R                  

The following release notes identify the critical open issues and the resolved issues for the 2210 release for your Azure Stack Edge devices. Features and issues that correspond to a specific model of Azure Stack Edge are called out wherever applicable.

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.

This article applies to the Azure Stack Edge 2210 release, which maps to software version 2.2.2111.1002. This software can be applied to your device if you're running Azure Stack Edge 2207 or later (2.2.2026.5318).

What's new

The 2210 release has the following features and enhancements:

  • High performance network VM enhancements:
    • When you deploy high performance network (HPN) VMs, vCPUs are automatically reserved using a default SkuPolicy. If a vCPU reservation was defined in an earlier version, and if you update the device to 2210, then that existing reservation is carried forth to 2210. For more information, see how to Deploy HPN VMs on your Azure Stack Edge.
    • Added support for bulk network configuration changes. For example, you now can edit multiple virtual switches and multiple virtual networks in the local UI. This improvement will reduce network configuration time.
    • Added HPN GPU VM sizes for T4 and A2 GPUs and Standard_F4s_v1 VM size. See the updated article at VM sizes and types for Azure Stack Edge Pro.
  • Kubernetes security updates - This release includes security updates and security hardening improvements for Kubernetes VMs.

If you have questions or concerns, open a support case through the Azure portal.

Issues fixed in this release

No. Feature Issue
1. Networking Open vSwitch Database Management Protocol (OVSDB) connection failure caused by stale node IP after user changed physical net adapter link status.

Known issues in this release

No. Feature Issue Workaround/comments
1. Preview features For this release, the following features are available in preview:
- Clustering and Multi-Access Edge Computing (MEC) for Azure Stack Edge Pro GPU devices only.
- VPN for Azure Stack Edge Pro R and Azure Stack Edge Mini R only.
- Local Azure Resource Manager, VMs, Cloud management of VMs, Kubernetes cloud management, and Multi-process service (MPS) for Azure Stack Edge Pro GPU, Azure Stack Edge Pro R, and Azure Stack Edge Mini R.
These features will be generally available in later releases.
2. Azure Kubernetes service on Azure Stack Edge When updating your device from 2209 to 2210, after the update is complete, the Kubernetes worker node may go down. Updating to 2301 will resolve this issue.

Known issues from previous releases

The following table provides a summary of known issues carried over from the previous releases.

No. Feature Issue Workaround/comments
1. Azure Stack Edge Pro + Azure SQL Creating SQL database requires Administrator access. Do the following steps instead of Steps 1-2 in Create-the-sql-database.
1. In the local UI of your device, enable compute interface. Select Compute > Port # > Enable for compute > Apply.
2. Download sqlcmd on your client machine from SQL command utility.
3. Connect to your compute interface IP address (the port that was enabled), adding a ",1401" to the end of the address.
4. Final command will look like this: sqlcmd -S {Interface IP},1401 -U SA -P "Strong!Passw0rd". After this, steps 3-4 from the current documentation should be identical.
2. Refresh Incremental changes to blobs restored via Refresh are NOT supported For Blob endpoints, partial updates of blobs after a Refresh, may result in the updates not getting uploaded to the cloud. For example, sequence of actions such as:
1. Create blob in cloud. Or delete a previously uploaded blob from the device.
2. Refresh blob from the cloud into the appliance using the refresh functionality.
3. Update only a portion of the blob using Azure SDK REST APIs. These actions can result in the updated sections of the blob to not get updated in the cloud.
Workaround: Use tools such as robocopy, or regular file copy through Explorer or command line, to replace entire blobs.
3. Throttling During throttling, if new writes to the device aren't allowed, writes by the NFS client fail with a "Permission Denied" error. The error will show as below:
hcsuser@ubuntu-vm:~/nfstest$ mkdir test
mkdir: can't create directory 'test': Permission denied​
4. Blob Storage ingestion When using AzCopy version 10 for Blob storage ingestion, run AzCopy with the following argument: Azcopy <other arguments> --cap-mbps 2000 If these limits aren't provided for AzCopy, it could potentially send a large number of requests to the device, resulting in issues with the service.
5. Tiered storage accounts The following apply when using tiered storage accounts:
- Only block blobs are supported. Page blobs aren't supported.
- There's no snapshot or copy API support.
- Hadoop workload ingestion through distcp isn't supported as it uses the copy operation heavily.
6. NFS share connection If multiple processes are copying to the same share, and the nolock attribute isn't used, you may see errors during the copy.​ The nolock attribute must be passed to the mount command to copy files to the NFS share. For example: C:\Users\aseuser mount -o anon \\\mnt\vms Z:.
7. Kubernetes cluster When applying an update on your device that is running a Kubernetes cluster, the Kubernetes virtual machines will restart and reboot. In this instance, only pods that are deployed with replicas specified are automatically restored after an update. If you have created individual pods outside a replication controller without specifying a replica set, these pods won't be restored automatically after the device update. You'll need to restore these pods.
A replica set replaces pods that are deleted or terminated for any reason, such as node failure or disruptive node upgrade. For this reason, we recommend that you use a replica set even if your application requires only a single pod.
8. Kubernetes cluster Kubernetes on Azure Stack Edge Pro is supported only with Helm v3 or later. For more information, go to Frequently asked questions: Removal of Tiller.
9. Kubernetes Port 31000 is reserved for Kubernetes Dashboard. Port 31001 is reserved for Edge container registry. Similarly, in the default configuration, the IP addresses and, are reserved for Kubernetes service and Core DNS service respectively. Don't use reserved IPs.
10. Kubernetes Kubernetes doesn't currently allow multi-protocol LoadBalancer services. For example, a DNS service that would have to listen on both TCP and UDP. To work around this limitation of Kubernetes with MetalLB, two services (one for TCP, one for UDP) can be created on the same pod selector. These services use the same sharing key and spec.loadBalancerIP to share the same IP address. IPs can also be shared if you have more services than available IP addresses.
For more information, see IP address sharing.
11. Kubernetes cluster Existing Azure IoT Edge marketplace modules may require modifications to run on IoT Edge on Azure Stack Edge device. For more information, see Run existing IoT Edge modules from Azure Stack Edge Pro FPGA devices on Azure Stack Edge Pro GPU device.
12. Kubernetes File-based bind mounts aren't supported with Azure IoT Edge on Kubernetes on Azure Stack Edge device. IoT Edge uses a translation layer to translate ContainerCreate options to Kubernetes constructs. Creating Binds maps to hostpath directory and thus file-based bind mounts can't be bound to paths in IoT Edge containers. If possible, map the parent directory.
13. Kubernetes If you bring your own certificates for IoT Edge and add those certificates on your Azure Stack Edge device after the compute is configured on the device, the new certificates aren't picked up. To work around this problem, you should upload the certificates before you configure compute on the device. If the compute is already configured, Connect to the PowerShell interface of the device and run IoT Edge commands. Restart iotedged and edgehub pods.
14. Certificates In certain instances, certificate state in the local UI may take several seconds to update. The following scenarios in the local UI may be affected.
- Status column in Certificates page.
- Security tile in Get started page.
- Configuration tile in Overview page.
15. Certificates Alerts related to signing chain certificates aren't removed from the portal even after uploading new signing chain certificates.
16. Web proxy NTLM authentication-based web proxy isn't supported.
17. Internet Explorer If enhanced security features are enabled, you may not be able to access local web UI pages. Disable enhanced security, and restart your browser.
18. Kubernetes Kubernetes doesn't support ":" in environment variable names that are used by .NET applications. This is also required for Event Grid IoT Edge module to function on Azure Stack Edge device and other applications. For more information, see ASP.NET core documentation. Replace ":" by double underscore. For more information,see Kubernetes issue
19. Azure Arc + Kubernetes cluster By default, when resource yamls are deleted from the Git repository, the corresponding resources aren't deleted from the Kubernetes cluster. To allow the deletion of resources when they're deleted from the git repository, set --sync-garbage-collection in Arc OperatorParams. For more information, see Delete a configuration.
20. NFS Applications that use NFS share mounts on your device to write data should use Exclusive write. That ensures the writes are written to the disk.
21. Compute configuration Compute configuration fails in network configurations where gateways or switches or routers respond to Address Resolution Protocol (ARP) requests for systems that don't exist on the network.
22. Compute and Kubernetes If Kubernetes is set up first on your device, it claims all the available GPUs. Hence, it isn't possible to create Azure Resource Manager VMs using GPUs after setting up the Kubernetes. If your device has 2 GPUs, then you can create one VM that uses the GPU and then configure Kubernetes. In this case, Kubernetes will use the remaining available one GPU.
23. Custom script VM extension There's a known issue in the Windows VMs that were created in an earlier release and the device was updated to 2103.
If you add a custom script extension on these VMs, the Windows VM Guest Agent (Version 2.7.41491.901 only) gets stuck in the update causing the extension deployment to time out.
To work around this issue:
1. Connect to the Windows VM using remote desktop protocol (RDP).
2. Make sure that the waappagent.exe is running on the machine: Get-Process WaAppAgent.
3. If the waappagent.exe isn't running, restart the rdagent service: Get-Service RdAgent | Restart-Service. Wait for 5 minutes.
4. While the waappagent.exe is running, kill the WindowsAzureGuest.exe process.
5. After you kill the process, the process starts running again with the newer version.
6. Verify that the Windows VM Guest Agent version is 2.7.41491.971 using this command: Get-Process WindowsAzureGuestAgent | fl ProductVersion.
7. Set up custom script extension on Windows VM.
24. Multi-Process Service (MPS) When the device software and the Kubernetes cluster are updated, the MPS setting isn't retained for the workloads. Re-enable MPS and redeploy the workloads that were using MPS.
25. Wi-Fi Wi-Fi doesn't work on Azure Stack Edge Pro 2 in this release.

Next steps