Undocumented configs for winrm

[javadevmtl]

Vagrant version

1.8.4

Host operating system

Ubuntu 14.04

Guest operating system

Windows Server 2008 with nsidc/vSphere plugin

The VM is launched and sysprep kicks in which causes the Windows VM to take longer to boot and it also reboots a couple times until sysprep is done.

The winrm communicator fails with No route to host, with a retry every 2 seconds based on what is seen from the INFO logs. But the VM in vSphere is up and running coretcly. A second, manual call after checking if sysprep completed, vagrant up call marks the machine as ready.

Google brought me to the original WinRB plugin. config.winrm.max_tries seems to do the trick. None of the "timeout" configs helped.

    config.winrm.max_tries = 100 <--- This worked
    config.winrm.timeout = 300 <--- doesn't seem to do anything

config.winrm.max_tries is not documented in the official docs. Maybe it can be documented with a tip indicating what the default is and to bump it up if syspreping?

Thanks

[dragon788]

Nice find! The WinRM timeout only affects how long Vagrant waits for the WinRM service (via plugin) to respond before failing.

[chrisroberts]

Fixed via #8102

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.