Skip to content

Commit 09dc408

Browse files
committed
New section for 'VM creation fails' linked from release notes.
1 parent db41e19 commit 09dc408

File tree

3 files changed

+52
-2
lines changed

3 files changed

+52
-2
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ The 2407 release has the following new features and enhancements:
6969

7070
| No. | Feature | Issue | Workaround/comments |
7171
| --- | --- | --- | --- |
72-
|**1.**|VM creation | Image directory is still the old location causing VM creation failure on Azure Stack Edge 2403. | |
72+
|**1.**|VM creation | Image directory is still the old location causing VM creation failure on Azure Stack Edge 2403. | Delete the Marketplace image and then create a new image from Azure portal. For detailed steps, see [Troubleshoot VM creation issues](azure-stack-edge-gpu-troubleshoot-virtual-machine-provisioning.md#vm-creation-fails). |
7373

7474
## Known issues from previous releases
7575

articles/databox-online/azure-stack-edge-gpu-troubleshoot-virtual-machine-provisioning.md

Lines changed: 51 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: v-dalc
77
ms.service: databox
88
ms.subservice: edge
99
ms.topic: troubleshooting
10-
ms.date: 03/24/2023
10+
ms.date: 08/15/2024
1111
ms.author: alkohli
1212
---
1313
# Troubleshoot VM deployment in Azure Stack Edge Pro GPU
@@ -169,6 +169,56 @@ To verify whether the network interface was created successfully, do these steps
169169

170170
This section covers common issues that occur during VM creation.
171171

172+
### VM creation fails
173+
174+
**Error description:** If you have a Marketplace image created with Azure Stack Edge 2403 or earlier, or if you updated to Azure Stack Edge 2403 release, and then tried to create a VM from the existing Marketplace image, your VM creation will fail, because this release changed the download path for the Marketplace image.
175+
176+
**Suggested solution:** Use the following steps to delete the existing Marketplace image, and then create a new Marketplace image from Azure portal.
177+
178+
1. From Azure portal, delete the existin Marketplace image.
179+
180+
1. List the ingestion and the BlobDownload ingestion job for the Marketplace image. Use these steps to [Connect to ARM](azure-stack-edge-gpu-connect-resource-manager.md?tabs=Az). Run the following script to list ingestion jobs:
181+
182+
Specify the subscription ID in the following Uri:
183+
184+
$uri1 = "https://management.<appliance name>.<DNS domain>/subscriptions/<sid>/providers/Microsoft.AzureBridge/locations/DBELocal/ingestionJobs/?api-version=2022-03-01
185+
186+
```powershell
187+
Function Get-AzCachedAccessToken()
188+
{
189+
$ErrorActionPreference = 'Stop'
190+
$azureRmProfile = [Microsoft.Azure.Commands.Common.Authentication.Abstractions.AzureRmProfileProvider]::Instance.Profile
191+
$currentAzureContext = Get-AzContext
192+
$profileClient = New-Object Microsoft.Azure.Commands.ResourceManager.Common.RMProfileClient($azureRmProfile)
193+
Write-Debug ("Getting access token for tenant" + $currentAzureContext.Subscription.TenantId)
194+
$token = $profileClient.AcquireAccessToken($currentAzureContext.Subscription.TenantId)
195+
$token.AccessToken
196+
}
197+
198+
$token = Get-AzCachedAccessToken
199+
$headers = @{Authorization = "Bearer $token"; "Content-Type" = "application/json" }
200+
$v = Invoke-RestMethod -Method Get -Uri $uri1 -Headers $headers
201+
v.value
202+
```
203+
204+
1. Find the ingestion job name = `Marketplace image sku name` and kind = `BlobDownload`.
205+
206+
Example: ingestion job name = `Ubuntu-18-04` and kind = `BlobDownload`.
207+
208+
![Screenshot of example syntax to find ingestion job name.](./media/azure-stack-edge-gpu-troubleshoot-virtual-machine-provisioning/ingestion-job-name.png)
209+
210+
1. If the ingestion job is found in Step 1, use the following steps to delete the ingestion job.
211+
212+
1. Run the following commands to delete image. For example, the ingestion job name in the example above is `ubuntu-18-04`. Additionally, `Subscription ID` and `Resource group` name can be found in the example.
213+
214+
```powershell
215+
$uri2 = "https://management.<appliance name>.<DNS domain>/subscriptions/sid/resourceGroups/rgname/providers/Microsoft.AzureBridge/locations/dbelocal/ingestionJobs/<ingestion job name>?api-version=2018-06-01"
216+
217+
Invoke-RestMethod -Method DELETE -Uri $uri2 -Headers $headers
218+
```
219+
220+
1. Create a new Marketplace image from Azure portal.
221+
172222
### Not enough memory to create the VM
173223
174224
**Error description:** When VM creation fails because of insufficient memory, you'll see the following error.
Loading

0 commit comments

Comments
 (0)