-
Notifications
You must be signed in to change notification settings - Fork 96
Description
I am using Azure-ARM to create a windows server 2022
Image creation all good, at the end, after creating managed image, while extracting VHD there is a error
Capturing image ...
Image ResourceGroupName : '_Image_2025'
Image Name : '-2025-10-08-0100'
Image Location : 'eastus'
VM Internal ID : '123456754-ee04-4a1e-8181-ffede32fkddie'
OS Disk ...
osDiskName : 'pkrosoz23egj1lh'
Capturing VHD ...
accessUri : 'https://md-hdd-nwls4nbtrrtb.z40.blob.storage.azure.net/sfhpxb23bqjx/abcd?sv=2018-03-28&sr=b&si=0aa9181d-8c7d-4bd2-ac2a-af712acb25d1&sig=f2s%2FjvItYsUef2bjs%2Fjtxtn34ilhAs8dpwuWVo1Kiw0%3D'
Copying VHD to Storage Account ...
Storage Container Name : 'images'
VHD Name : 'pkrosoz23egj1lh.vhd'
failed to capture OS Disk with err : failed to copy to storage with err : error copying: waiting for file to copy: context deadline exceeded
Revoking access ...
Provisioning step had errors: Running the cleanup provisioner, if present...
When I check the status of the copying blob
I get this :
{
"completionTime": null,
"destinationSnapshot": null,
"id": "2222222-bd29-4123-a2bb-xxxxxxxa",
"incrementalCopy": null,
"progress": "15099494400/322122547712",
"source": "https://md-hdd-hpjk4stz1bdr.z5.blob.storage.azure.net/dxfw5g5cvnbc/abcd?sv=2018-03-28&sr=b&si=f2368edf-750b-45d0-b523-52065491cde8",
"status": "failed",
"statusDescription": "403 AuthenticationFailed "Copy failed when reading the source.""
}
Looks like in mid copy the failure happens.. may be because of the time? i am not able to set caputure time limit!
Any suggestion is greatly appreciated.