Open tboyce opened 8 years ago
Thanks @tboyce, could you please provide a Gist containing a debug log for this when it breaks again? Instructions for verbose logging can be found here: https://www.vagrantup.com/docs/other/debugging.html
Also, if you could please provide some detail on your OS version and anything else that might be relevant that would be great. I'm going to guess Windows 8.1 based on that box name though!
Seems like there might be some potentially sensitive data in the debug log. If I can find the time I will see if I can reproduce in a clean environment. The host and guest OS are both Windows 8.1 and I am using VirtualBox and winrm to communicate.
Thanks Tim. If it's easier feel free to obfuscate the data.
On Fri, Mar 4, 2016 at 12:59 AM, Timothy Boyce notifications@github.com wrote:
Seems like there might be some potentially sensitive data in the debug log. If I can find the time I will see if I can reproduce in a clean environment. The host and guest OS are both Windows 8.1 and I am using VirtualBox and winrm to communicate.
— Reply to this email directly or view it on GitHub https://github.com/SEEK-Jobs/vagrant-windows-domain/issues/10#issuecomment-191771416 .
Matt Fellows
Looks to be related to #16
Great plugin, but I am having an issue with destroying VMs. When I destroy, with the VM up, it asks for credentials to remove the computer from the domain as expected, and then it reboots. Vagrant then appears to be sitting and waiting for the machine to shutdown, which never happens.
After waiting for a few minutes vagrant prints this error: