Vagrantfile w/o cachier statement fails to start

[miketheman]

In a default Vagrantfile, with both Vagrant 1.2.4 and 1.2.7, vagrant-cachier 0.3.0

Fails with:

.vagrant.d/gems/gems/vagrant-cachier-0.3.0/lib/vagrant-cachier/action/ensure_single_cache_root.rb:24:in cache_scoped_to_machine?': undefined methodto_sym' for #Object:0x00000100facb88 (NoMethodError)

Full stacktrace on gist: https://gist.github.com/miketheman/6213503

Uninstalling vagrant-cachier allows me to continue.

[fgrehm]

@miketheman yup, my bad =/ that should be fixed on master by now after https://github.com/fgrehm/vagrant-cachier/commit/e46a3c398b314771b061aeb7105258be841e4878, are you able to build and install the plugin from sources while we don't release a new version? I might get to that later on tonight

[miketheman]

Is there instructions on how to install a vagrant-plugin from github, instead of from the 'normal' source?

[fgrehm]

@miketheman I'll add it to the readme later but you can follow the same instructions from vagrant-lxc: https://github.com/fgrehm/vagrant-lxc/wiki/Development#installing-the-plugin-from-source :)

[fgrehm]

@miketheman I've just released 0.3.1, please let us know if it is still an issue for you so we can reopen the issue

[miketheman]

@fgrehm Just tried 0.3.1, getting same issue.

[fgrehm]

@miketheman that's pretty weird, I just tried with the following dead simple Vagrantfile under both the lxc provider and the default vbox provider and things are working just fine oO

Vagrant.configure('2') do |config|
  config.vm.box = 'quantal64'
end

How does your Vagrantfile looks like? This is the code that I changed to fix the issue and is exactly the same line that you pointed out on the issue description. Did the error message changed?

[miketheman]

@fgrehm It looks like there might be something that triggers this bug with the Chef provisioner.

Add this to your Vagrantfile to repro:

  config.vm.provision :chef_solo do |chef|
  end

No recipe needed, just the definition of a provisioner triggers the behavior.

[fgrehm]

Ok, I'll reopen the issue and will investigate later on tonight. Tks for the info and sorry about that

[fgrehm]

@miketheman I've got a fix :) expect 0.3.2 at some point between tonight and tomorrow as I'll try to write some Bats tests before releasing in order to have a sanity check while we don't have unit testing around

[fgrehm]

@miketheman 0.3.2 is out! hopefully this has been fixed once and for all :D

[miketheman]

Confirming that the behavior seen no longer occurs with 0.3.2. Thank @fgrehm!

On Wed, Aug 14, 2013 at 11:50 PM, Fabio Rehm notifications@github.comwrote:

@miketheman https://github.com/miketheman 0.3.2 is out! hopefully this has been fixed once and for all :D

— Reply to this email directly or view it on GitHubhttps://github.com/fgrehm/vagrant-cachier/issues/41#issuecomment-22683702 .