Skip to content

Commit 9577171

Browse files
Merge pull request #18486 from MicrosoftDocs/main
Auto Publish – main to live - 2025-07-18 22:00 UTC
2 parents a4486f1 + b980a76 commit 9577171

File tree

3 files changed

+156
-8
lines changed

3 files changed

+156
-8
lines changed

AKS-Arc/delete-storage-volume.md

Lines changed: 18 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,9 @@ description: Learn how to mitigate issues after deleting storage volumes.
44
author: sethmanheim
55
ms.author: sethm
66
ms.topic: troubleshooting
7-
ms.date: 02/28/2025
7+
ms.date: 07/18/2025
8+
ms.reviewer: guanghu
9+
ms.lastreviewed: 07/18/2025
810

911
---
1012

@@ -18,10 +20,22 @@ AKS Arc workload data is stored on Azure Local storage volumes, including the AK
1820

1921
## Workaround
2022

21-
To manage storage volumes on Azure Local, follow these steps:
23+
If the storage volume is accidentally deleted, you can mitigate the issue by recreating the storage path using the Azure CLI. For more information, see [Create storage path for Azure Local](/azure/azure-local/manage/create-storage-path). For example:
2224

23-
- Ensure that you deleted all the storage path(s) that are created on that storage volume. Deleting storage paths raises an alert to indicate the workload that was stored on it. To delete the storage path, see [Delete a storage path](/azure/azure-local/manage/create-storage-path?view=azloc-24112&preserve-view=true&tabs=azurecli#delete-a-storage-path).
24-
- If you have an AKS Arc cluster that must be deleted, see [Delete the AKS Arc cluster](aks-create-clusters-cli.md#delete-the-cluster).
25+
```azurecli
26+
$storagepathname="<Storage path name>"
27+
$path="<Path on the disk to cluster shared volume>"
28+
$subscription="<Subscription ID>"
29+
$resource_group="<Resource group name>"
30+
$customLocName="<Custom location of your Azure Local>"
31+
$customLocationID="/subscriptions/<Subscription ID>/resourceGroups/$resource_group/providers/Microsoft.ExtendedLocation/customLocations/$customLocName"
32+
$location="<Azure region where the system is deployed>"
33+
34+
az stack-hci-vm storagepath create --resource-group $resource_group --custom-location $customLocationID --name $storagepathname --path $path
35+
az stack-hci-vm storagepath update --resource-group $resource_group --custom-location $customLocationID --name $storagepathname --location $location
36+
```
37+
38+
Once the storage path is recreated, the [MOC service](concepts-node-networking.md#microsoft-on-premises-cloud-service) automatically re-downloads the required **MocGalleryImages**.
2539

2640
## Next steps
2741

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

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,8 @@ 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: how-to
7-
ms.date: 02/11/2025
7+
ms.date: 07/18/2025
88
ms.author: sethm
9-
ms.lastreviewed: 03/18/2020
109

1110
# Intent: As an Azure Stack operator, I want to learn about servicing policy and how to keep an integrated system supported.
1211
# Keyword: servicing policy azure stack
@@ -26,8 +25,6 @@ Full update packages are hosted in a secure Azure endpoint. You can download the
2625

2726
Hotfix update packages are hosted in the same secure Azure endpoint. You can download them using the embedded links in each of the respective hotfix KB articles; for example, [Azure Stack Hub Hotfix 1.1809.12.114](https://support.microsoft.com/help/4481548/azure-stack-hotfix-1-1809-12-114). Similar to the full, monthly update packages, Azure Stack Hub operators can download the .xml and .zip files and import them using the procedure in [Apply updates in Azure Stack Hub](azure-stack-apply-updates.md). Azure Stack Hub operators with connected scale units will see the hotfixes automatically appear in the administrator portal with the message **Update available**.
2827

29-
If your scale unit isn't connected and you want to be notified about each hotfix release, subscribe to the [RSS feed](https://azurestackhubdocs.azurewebsites.net/xml/hotfixes.rss) to be notified about each hotfix release.
30-
3128
## Update package types
3229

3330
There are two types of update packages for integrated systems:
@@ -86,6 +83,8 @@ For example, if the most recent update version available is 2501 (N), the two pr
8683

8784
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.
8885

86+
:::image type="content" source="media/azure-stack-servicing-policy/servicing-policy-workflow.svg" alt-text="Diagram showing Azure Stack Hub servicing policy workflow." lightbox="media/azure-stack-servicing-policy/servicing-policy-workflow.svg":::
87+
8988
### Resource provider version support
9089

9190
For Azure Stack Hub resource providers, it's important to note that only the most recently released version of a given resource provider that is compatible with your supported version of Azure Stack Hub is supported, even though you may be using an older version of Azure Stack Hub that is still within the support window.
Lines changed: 135 additions & 0 deletions
Loading

0 commit comments

Comments
 (0)