Open chrisgannon6 opened 7 years ago
Tested with 2.0.0. Result is the same.
Interesting, I'm running into a similar issue with Fusion. Right after I issue the command to join the domain, it drops the winrm connection:
==> win10: VERBOSE: Performing the operation "Join in domain 'windomain.local'" on target "win10".
DEBUG winrmshell: [WinRM] Waiting for output...
DEBUG winrmshell: [WinRM] Processing output
INFO interface: info: HasSucceeded : True
INFO interface: info: ==> win10: HasSucceeded : True
==> win10: HasSucceeded : True
INFO interface: info: ComputerName : win10
INFO interface: info: ==> win10: ComputerName : win10
==> win10: ComputerName : win10
INFO interface: info: WARNING: The changes will take effect after you restart the computer win10.
INFO interface: info: ==> win10: WARNING: The changes will take effect after you restart the computer win10.
==> win10: WARNING: The changes will take effect after you restart the computer win10.
DEBUG winrmshell: [WinRM] cleaning up command_id: 063F4777-58BC-4F4A-86E7-C8F9F358202D on shell_id 6AF10D1E-FD75-4201-983C-5D047DAAE8C6
ERROR warden: Error occurred: Vagrant timed out while attempting to connect via WinRM. This usually
means that the VM booted, but there are issues with the WinRM configuration
or network connectivity issues. Please try to `vagrant reload` or
`vagrant up` again.
Problem persists with 2.0.1 and vmware-fusion-plugin 5.0.4
Is there any update on this? Will this be fixed soon? It would help immensely if anyone can provide a workaround for Joining domain and running provisioners as domain user
This continues to be an issue with the vagrant-vmware-desktop plugin as well. Does anyone have any idea what the ultimate root cause of the problem is here or what debug steps can be taken to isolate the issue?
Vagrant version
Vagrant 1.9.8
Vagrant plugins
vagrant-share (1.1.9, system) vagrant-triggers (0.5.3)
Vagrant provider
VMWare Workstation 12.5.7
Host operating system
Windows 7 x64
Guest operating system
Windows Server 2016
Vagrantfile
Debug output
https://gist.github.com/chrisgannon6/eb8956196b35d83b4787408be6fba7fc
Expected behavior
Vagrant should find the correct IP address and connect to it via WinRM after rebooting. This used to work in earlier versions of Vagrant - the last version I tested working 1.8.1.
Actual behavior
After adding the VM to the domain, the VM reboots. Vagrant attempts to connect to the VM, but times out (at least 10 minutes after it was already available).
Steps to reproduce
Note: This only occurs with VMWare Workstation as the provider. It does not occur when vsphere is the provider. Suspect this has to do with the fact Workstation has a public network defined for it. However this used to work fine in Vagrant 1.8.1.
Also have tried a number of configuration options to attempt to resolve this. eg. - setting enable_vmrun_ip_lookup = false
References
Are there any other GitHub issues (open or closed) that should be linked here? For example: