Kitchen ShellOut to Vagrant with Bundler 1.6.0 install fails

[martinisoft]

After upgrading Vagrant to 1.5.1, then upgrading Bundler to 1.6.0, I can no longer use kitchen setup/test commands. Downgrading to Bundler 1.5.3 has temporarily resolved the problem, but it seems there is a temporary problem with a breaking change to their API.

>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ShellOut::ShellCommandFailed
>>>>>> Message: Expected process to exit with [0], but received '1'
---- Begin output of vagrant --version ----
STDOUT:
STDERR: /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/bundler.rb:31:in `initialize': undefined method `new' for Bundler::UI:Module (NoMethodError)
        from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/bundler.rb:17:in `new'
        from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/bundler.rb:17:in `instance'
        from /Applications/Vagrant/bin/../embedded/gems/gems/vagrant-1.5.1/lib/vagrant/pre-rubygems.rb:22:in `<main>'
---- End output of vagrant --version ----
Ran vagrant --version returned 1
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try running `kitchen diagnose --all` for configuration

[fnichol]

Oh dear, I will take a look at that this morning. It could be an issue in Mixlib::ShellOut as well. Thank you for reporting!

[martinisoft]

Welcome! Seems there was a similar issue reported to Vagrant, but think this is isolated to Test Kitchen.

[sethvargo]

@martinisoft do you have a link to the Vagrant issue for xlinking?

[notapatch]

Vagrant are not ready to go to [bundler] 1.6.1 -mitchellh
Vagrant gemspec has been set bundler to ~> 1.5.2

[ryancragun]

This was fixed for me with a Vagrant 1.5.4 update.

[aspiers]

Looks like this was broken by rubygems/bundler@5e38e2d7. I would have expected bundler to follow semantic versioning but maybe I misunderstood something.