-
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
Vagrant 1.8.7 breaks Salt Provisioner Plugin #8005
Comments
@RobertDeRose you can manually patch in vagrant 1.8.7 line number 9 is: OPTIMISTIC_PATH_DEFAULTS = Hash[[ change it to : OPTIMISTIC_PATH_DEFAULTS = Hash[*[ Seem like it's fix on master |
@jespada Thanks for the workaround, but it appears 1.8.7 just didn't do enough QA before going out, there are too many issues and I've rolled back to 1.8.6 for a stable experience. Hopefully, 1.8.8 will be out soon and will have gone through better QA. |
Fixed via #7986 |
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. |
This appears to just be broken, due to changes in the 1.8.7 version of vagrant and it didn't include those changes in the Salt provisioner. Reproduced on two different employee laptops with the same configuration, only difference is one is using VirtualBox the other VMware Fusion 8. Both error out with the same exact issue.
Vagrant file doesn't seem to matter either, just needs to be a box that uses Salt for provisioning to cause the error.
Vagrant version
1.8.7
Host operating system
10.12.1 (16B2555)
Guest operating system
bento/debian-7.11
Vagrantfile
Backtrace output showing the issue
https://gist.github.com/RobertDeRose/976a6d997cb5f5f7e37cc7813556af33
Expected behavior
For it not to blow up.
Actual behavior
/opt/vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/provisioners/salt/provisioner.rb:43:in `initialize': no implicit conversion of Object into String (TypeError)
Steps to reproduce
The text was updated successfully, but these errors were encountered: