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: azure-local/known-issues.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Release notes with fixed and known issues in Azure Local
3
3
description: Read about the known issues and fixed issues in Azure Local.
4
4
author: alkohli
5
5
ms.topic: conceptual
6
-
ms.date: 06/09/2025
6
+
ms.date: 06/10/2025
7
7
ms.author: alkohli
8
8
ms.reviewer: alkohli
9
9
---
@@ -70,7 +70,7 @@ The following table lists the known issues in this release:
70
70
|Feature |Issue |Workaround |
71
71
|---------|---------|---------|
72
72
| Update <!--54889342-->| A critical VM operational status not OK alert is shown in the Azure portal under **Update readiness** and in the **Alerts** pane after the update has completed successfully. Additionally, the alert appears when running the `Get-HealthFault` cmdlet. | No action is required on your part. This alert will resolve automatically in a few days. |
73
-
| Deployment <!-- 33153622-->| Updating Azure Arc extensions out of band from the **Azure Local Machine** page via the Azure portal will result in issues during deployment. The extensions that shouldn't be updated out of band are: `AzureEdgeDeviceManagement`, `AzureEdgeLifecycleManager`, and `AzureEdgeAKVBackupForWindows`. |The correct versions of these extensions are automatically installed during deployment. |
73
+
| Deployment <!-- 33153622-->| Updating Azure Arc extensions out-of-band from the Azure Local Machine page via the Azure portal will result in issues during deployment. The extensions that shouldn't be updated out-of-band are: `AzureEdgeDeviceManagement`, `AzureEdgeLifecycleManager`, and `AzureEdgeAKVBackupForWindows`. |Installing extensions out-of-band from the Azure Local machine page is not supported. |
The manual extension upgrade works like the [Automatic extension upgrade](/azure/azure-arc/servers/manage-automatic-vm-extension-upgrade?tabs=azure-portal#how-does-automatic-extension-upgrade-work). On an Azure Local Arc-enabled cluster, when you manually upgrade an extension, Azure saves the version you've selected. Azure then attempts to upgrade the extension on all nodes in the cluster to that version.
389
389
390
-
On some servers, if the extension upgrade fails the platform attempts to upgrade to the selected version during the next [Azure Local cloud sync](../faq.yml).
391
-
392
-
> [!NOTE]
393
-
> Updating Azure Arc extensions out of band from the **Azure Local Machine** page from the Azure portal will result in issues during deployment.
390
+
On some servers, if the extension upgrade fails, the platform attempts to upgrade to the selected version during the next [Azure Local cloud sync](../faq.yml).
394
391
395
392
Use the manual workflow in these scenarios:
396
393
@@ -407,6 +404,11 @@ To manually upgrade an extension, follow these steps:
407
404
408
405
3. Choose the latest version and select **Save**.
409
406
407
+
> [!NOTE]
408
+
> Updating Azure Arc extensions out-of-band from the Azure Local Machine page via the Azure portal may result in issues during deployment. The extensions that shouldn't be updated out-of-band are: `AzureEdgeDeviceManagement`, `AzureEdgeLifecycleManager`, and `AzureEdgeAKVBackupForWindows` as shown in the figure.
409
+
410
+
:::image type="content" source="media/arc-extension-management/arc-extension-installation.png" alt-text="Screenshot of how to manually upgrade an extension in the Azure portal." lightbox="media/arc-extension-management/arc-extension-installation.png":::
411
+
410
412
### Disable automatic extension upgrade
411
413
412
414
You can disable automatic upgrades for certain extensions in the Azure portal. To disable automatic upgrades, navigate to the **Extensions** page and perform these steps:
0 commit comments