-
Notifications
You must be signed in to change notification settings - Fork 112
Hanging on WinRM #241
Comments
I've run into this same issue as well trying to deploy a Windows 2016 image on Azure. I enabled debug to see what was happening. It appears to check indefinitely for WinRM port to become "ready". This doesn't appear to be a networking issue since I was able to open a telnet connection to the configured WinRM port (TCP 5986) as well as RDP (TCP 3389) from my workstation via the FQDN and Public IP of the VM. MacOS Here's the interesting bits of the Vagrantfile that I'm using: Vagrant.configure('2') do |config|
config.vm.box = 'azure'
config.vm.provider :azure do |azure, override|
override.vm.synced_folder ".", "/vagrant", disabled: true
...
azure.vm_image_urn = 'MicrosoftWindowsServer:WindowsServer:2016-Datacenter:latest'
override.winrm.transport = :ssl
override.winrm.port = 5986
override.winrm.ssl_peer_verification = false # must be false if using a self signed cert
end
end Here's the log entry that's repeated seeming indefinitely until the Vagrant run is stopped:
All Resources are properly provisioned in Azure including the NSG with the firewall ports. I'm not very proficient with Ruby but digging through the code has lead me to |
Same thing here. Anyone for help us ? |
Can you add this at your Vagrantfile : config.vm.guest = :windows ? |
I seem to be stuck waiting for WinRM. I'm pretty confident that this isn't a networking issue my end or in Azure as I've been building Packer images in the same subscription.
Can anyone help with this?
OS is OS X 10.15.2
Vagrant 2.2.5
The text was updated successfully, but these errors were encountered: