WinRM on VMWare Workstation - Proxy issue

[Denny Pruitt]

All,

I've spent the last few days troublshooting an issue where 'Waiting for WinRM to become available...' just keeps waiting.

My environment was CentOS with VMware Workstation installed.  Because the WinRM check uses http (i assume curl, i can't really read GO that well) and VMWare workstation creates a Virtual Nic and Virtual Switch it can be routed to the proxy before it routes to the local IP.

Unfortunately no_proxy doesnt' respect ip ranges, so you can't just add a block of ip's that get set dynamically to it.

I was going to create an issue about this, but it mentioned something about this email group for WinRM/SSH issues.

I suggest that the process needs to be changed so that either:
1) it dynamically adds the active hosts IP to the no_proxy variable in the active session,
or 
2) It can determine if it's using a local VMWare session, and then ignore the proxy in it's WinRM calls (for curl, it would be curl --noproxy "*").

Thanks,

Denny

[Denny Pruitt]

I've seen the issue come up a few times now that i know what to look for:

https://github.com/jetbrains-infra/packer-builder-vsphere/issues/150