-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Facing below error while creating VM from the image created #10054
Comments
Hi @sagarshitole01, |
{ {"code":"OSProvisioningTimedOut","message":"OS Provisioning for VM 'eheu2pd1epvmtestonly' did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, make sure the image has been properly prepared (generalized).\r\n * Instructions for Windows: https://azure.microsoft.com/documentation/articles/virtual-machines-windows-upload-image/ \r\n * Instructions for Linux: https://azure.microsoft.com/documentation/articles/virtual-machines-linux-capture-image/ \r\n * If you are deploying more than 20 Virtual Machines concurrently, consider moving your custom image to shared image gallery. Please refer to https://aka.ms/movetosig for the same."} |
@sagarshitole01 Please share packer file and complete log file to understand your issue. |
above are the image creation logs |
Kindly follow the instructions as mentioned above link. |
@sagarshitole01 could you please provide your comments. |
Hi @sagarshitole01 we tried to follow-up for your response, hopefully issue got resolved with provided instructions. We are closing the issue as of now, Thanks. |
Description
Facing below error while creating VM from the image created
"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."
I am using below script for creating image$(SubscriptionId) -ResourceGroupName "$ (ResourceGroupName)" -ImageGenerationRepositoryRoot "$(System.DefaultWorkingDirectory)/_actions_runner-images" -ImageType $(ImageType) -AzureLocation "$ (AzureLocation)" -AzureClientId $(AzureClientId) -AzureClientSecret $ (AzureClientSecret) -AzureTenantId $(AzureTenantId) -Force
Import-Module $(System.DefaultWorkingDirectory)/_actions_runner-images/helpers/GenerateResourcesAndImage.ps1
GenerateResourcesAndImage -SubscriptionId
and below script to add image version under image definition$(DestinationResourceGroupName) --gallery-name $ (GalleryName) --gallery-image-definition $(GalleryImageDefinitionName) --gallery-image-version $ (GalleryImageVersionName) --managed-image $(ManagedImage) --target-regions $ (GalleryImageDefinitionLocation)
az sig image-version create --resource-group
Platforms affected
Runner images affected
Image version and build link
[RELEASE_ARTIFACTS__ACTIONS_RUNNER-IMAGES_SOURCEVERSION] --> [25c57a1]
Is it regression?
NA
Expected behavior
VM is created without any errors attached
Actual behavior
Facing error when trying to create VM in azure portal using the image generated "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."
Repro steps
Step1:$(SubscriptionId) -ResourceGroupName "$ (ResourceGroupName)" -ImageGenerationRepositoryRoot "$(System.DefaultWorkingDirectory)/_actions_runner-images" -ImageType $(ImageType) -AzureLocation "$ (AzureLocation)" -AzureClientId $(AzureClientId) -AzureClientSecret $ (AzureClientSecret) -AzureTenantId $(AzureTenantId) -Force
Import-Module $(System.DefaultWorkingDirectory)/_actions_runner-images/helpers/GenerateResourcesAndImage.ps1
GenerateResourcesAndImage -SubscriptionId
Step2:$(DestinationResourceGroupName) --gallery-name $ (GalleryName) --gallery-image-definition $(GalleryImageDefinitionName) --gallery-image-version $ (GalleryImageVersionName) --managed-image $(ManagedImage) --target-regions $ (GalleryImageDefinitionLocation)
az sig image-version create --resource-group
Step3:
In azure portal I am trying to create a VM from the image generated in our compute image gallery
The text was updated successfully, but these errors were encountered: