This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(236.8, 37%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EV%3C/text%3E%3C/svg%3E)
Issue description:
When we run packer buid in the backend VM creates during this process we are seeing winrm time out issue
Error:
==> azure-arm.autogenerated_1: Removing the created Deployment object: 'kvpkrdpvdfu0h9tfg'
==> azure-arm.autogenerated_1:
==> azure-arm.autogenerated_1: The resource group was not created by Packer, not deleting ...
Build 'azure-arm.autogenerated_1' errored after 8 minutes 40 seconds: Timeout waiting for WinRM.
==> Wait completed after 8 minutes 40 seconds
==> Some builds didn't complete successfully and had errors:
--> azure-arm.autogenerated_1: Timeout waiting for WinRM.
==> Builds finished but no artifacts were created.
Also, if this is a packer related issue then you can report it here: https://github.com/hashicorp/packer/issues
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
HI Vipul, I am not seeing any private message you have sent
Hello Varma
Please refresh the browser and check the private message conversation.
Even I refresh and tried in private browser, I have no visibility to private messages.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(243.2, 24%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
Hi Varma, Are you using the private IP option for the VM? If so, run the packer.exe file from the same virtual network the packer vm is building on. If you are using a public ip, make sure that you don't have an NSG or firewall blocking the WinRM requests.
Hi Varma, Are you using the private IP option for the VM? If so, run the packer.exe file from the same virtual network the packer vm is building on. If you are using a public ip, make sure that you don't have an NSG or firewall blocking the WinRM requests.
Hello Varma
Welcome to Microsoft Q&A Platform, thanks for posting your query here.
Based on the details shared (issue related to the WinRM connection timing out while running the Packer build), this could happen if the WinRM service is not running or if there is a network connectivity issue between the Packer build machine and the target VM.
To troubleshoot this issue, you can try the following steps:
-Check if the WinRM service is running on the target VM.
-Check if the network connectivity between the Packer build machine and the target VM is working properly. You can do this by pinging the target VM from the Packer build machine and vice versa.
-Increase the WinRM timeout value in the Packer build configuration file.
If the issue persists, you can try using SSH instead of WinRM to connect to the target VM. To do this, you need to modify the Packer build configuration file to use SSH instead of WinRM. You can find more information on how to do this in the Packer documentation.
I hope this helps you resolve the issue.
HI Vipullag, Here is the VM name before winrom service to stat, you can see I have verified ping for that machine in the same machine where I am executing packer build
Increaseing time out did not work, Here is code of snippet I am using for winrm,
what exactly I should change the to use SSH, could you please provide those details so that I can update
os_type = "Windows"
subscription_id = "XXXXXX"
tenant_id = "XXXXXX"
vm_size = "Standard_D2_v4"
virtual_network_name = "XXXX"
virtual_network_resource_group_name = "XXXXX"
virtual_network_subnet_name = "BuildResults"
communicator = "winrm"
winrm_insecure = true
winrm_timeout = "120m"
winrm_use_ssl = true
winrm_username = "packer"
}
Looking forword for your response. Thank you
As I mentioned in my previous response, the details are available on packer documentation. Please check the packer documentation for the the same.
Sharing few for your reference:
https://developer.hashicorp.com/packer/docs/communicators/winrm
https://developer.hashicorp.com/packer/docs/communicators/ssh
https://developer.hashicorp.com/packer/docs/templates/legacy_json_templates/builders
Hi Vipul, Although SSH config set up why it is going to winrm