You can clone with
No one assigned
Hi, I'm having troubles with Chef solo and recipe_url.
Now, I'm getting this error:
[default] Running chef-solo...
[default] stdin: is not a tty
[default] /usr/lib/ruby/gems/1.8/gems/chef-0.9.12/bin/../lib/chef/application/solo.rb:157:in `join': stderr
[default] : : stderr
[default] can't convert nil into String: stderr
[default] (: stderr
[default] TypeError: stderr
[default] from /usr/lib/ruby/gems/1.8/gems/chef-0.9.12/bin/../lib/chef/application/solo.rb:157:in `reconfigure'
[default] from /usr/lib/ruby/gems/1.8/gems/chef-0.9.12/bin/../lib/chef/application.rb:60:in `run'
[default] from /usr/lib/ruby/gems/1.8/gems/chef-0.9.12/bin/chef-solo:25
[default] from /usr/bin/chef-solo:19:in `load'
[default] from /usr/bin/chef-solo:19
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
chef-solo -c /tmp/vagrant-chef-1/solo.rb -j /tmp/vagrant-chef-1/dna.json
The output of the command prior to failing is outputted below:
This is my current Vagrantfile:
Vagrant::Config.run do |config|
config.vm.box = "lucid64"
config.vm.box_url = "http://files.vagrantup.com/lucid64.box"
config.vm.provision :chef_solo do |chef|
chef.cookbooks_path = "cookbooks"
chef.recipe_url = "https://github.com/crowdint/vagrant-setup/raw/master/downloads/cookbooks.tar.gz"
config.vm.customize do |vm|
vm.memory_size = 1024
I'm using 1.9.2, and this are my gems:
1.9.2@vagrants (master)(default running)$ gem list
*** LOCAL GEMS ***
Seems to be related to my cookbook file, is there a specifications for that file/contents?
I don't see remarkable differences between this and mine.
What platform are you on? I want to try to take a look and see if I can reproduce this, but I think this can happen on Windows.
I'm on OSX Lion
$ uname -a
Darwin mariozaizar 11.2.0 Darwin Kernel Version 11.2.0: Tue Aug 9 20:54:00 PDT 2011; root:xnu-1699.24.8~1/RELEASE_X86_64 x86_64
Alright thanks, I'll give it a shot with your tar.gz later today, thanks!
Append folder name to chef solo cookbooks [GH-511]
Confirmed 0.8.8.dev fixes the issue. Thanks a lot. Please release soon.
The fix for this in 0.8.8 is causing a regression for setups that have a 'cookbooks' directory containing chef recipes instead of downloading the recipes through chef.recipe_url. The cookbook_path in solo.rb ends up as /tmp/vagrant-chef-1/chef-solo-1/cookbooks, but the 'cookbooks' directory from the host is mounted at /tmp/vagrant-chef-1/chef-solo-1/
This worked OK in 0.8.7. Should I open a separate issue?
Nevermind, I think this was caused by me upgrading from 0.8.7 to 0.8.8 without reloading the running Vagrant VM. The mount point Vagrant creates from scratch with a 'vagrant reload' or 'vagrant up' is correct.
Does the documentation have any notes about upgrading Vagrant?
Perhaps a quick note regarding correct procedure with respect to the care and feeding of already-created Vagrant VMs is in order. What should people expect after an upgrade of Vagrant? Should they reload their VMs? Terminate them before upgrade and restart them from scratch?