-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin winrm-fs is out of date and contains bugs (currently 0.3.2, latest version is 0.4.3) #7526
Comments
I manually updated winrm-fs 0.4.3 in vagrant 1.8.4 with these steps and I can work with it for a while. Only a minor issue is that some parts of the WinRM output is now visisble: |
Thanks @StefanScherer , I'll give those steps a go. |
@TheFrogDaddy but be warned as Seth mentioned in #7476 there may be new issues. I now have switched back to Vagrant 1.8.1 without any patches to it and using the embedded winrm-1.3.6 and winrm-fs 0.2.3. Ping me if someone needs this scenario and provision scripts to test against newer winrm/winrm-fs versions. |
@StefanScherer @TheFrogDaddy This may still be an issue in the underlying WinRb/WinRM gem, not sure if it is patched in the version you mention above as there is still an open issue, WinRb/winrm-fs#18. |
Hi there, It looks like this has been resolved within a previously shipped version of Vagrant so I am now closing this issue. If the original issue was not fully resolved, please reopen this issue or create a new one. Cheers! |
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. |
Vagrant version
1.8.4
Host operating system
OSX El Capitan
Guest operating system
Windows 10
Expected behavior
winrm-fs plugin be a recent version >= 4.0
Actual behavior
winrm-fs plugin is out of date and contains bugs which preventing provisioning of a windows box after installing chocolatey
References
This was my original issue, the devs of winrm-fs have informed me that the latest versions resolves my issue.
chocolatey/choco#834
The text was updated successfully, but these errors were encountered: