On Wednesday, September 19, 2018 at 1:32:40 PM UTC-4, Denny Pruitt wrote: > > 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 >
-- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/6fc13c4b-d84d-43d1-ad08-ed8336991281%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
