schubergphilis / vagrant-chef-zero

Vagrant Plugin for Chef Zero
Apache License 2.0
91 stars 41 forks source link

Not working on Vagrant 1.5.0 -- undefined method `scope' for #<Vagrant::UI::Colored:0x0000010133ecb0> (NoMethodError) #41

Closed c10l closed 10 years ago

c10l commented 10 years ago

Hey,

Just to give a heads up that since I upgraded Vagrant to 1.5 I'm getting this error:

/Users/cassiano/.vagrant.d/gems/gems/vagrant-chef-zero-0.6.0/lib/vagrant-chef-zero/env.rb:13:in `initialize': undefined method `scope' for #<Vagrant::UI::Colored:0x0000010133ecb0> (NoMethodError)
    from /Users/cassiano/.vagrant.d/gems/gems/vagrant-chef-zero-0.6.0/lib/vagrant-chef-zero/action.rb:37:in `new'
    from /Users/cassiano/.vagrant.d/gems/gems/vagrant-chef-zero-0.6.0/lib/vagrant-chef-zero/action.rb:37:in `block in chef_zero_ui_setup'
    from /Users/cassiano/.vagrant.d/gems/gems/vagrant-chef-zero-0.6.0/lib/vagrant-chef-zero/action.rb:36:in `tap'
    from /Users/cassiano/.vagrant.d/gems/gems/vagrant-chef-zero-0.6.0/lib/vagrant-chef-zero/action.rb:36:in `chef_zero_ui_setup'
    from /Users/cassiano/.vagrant.d/gems/gems/vagrant-chef-zero-0.6.0/lib/vagrant-chef-zero/plugin.rb:15:in `reconfig'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/action/runner.rb:45:in `call'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/action/runner.rb:45:in `block (2 levels) in run'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/action/runner.rb:44:in `tap'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/action/runner.rb:44:in `block in run'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/action/runner.rb:43:in `map'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/action/runner.rb:43:in `run'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/environment.rb:300:in `hook'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/environment.rb:141:in `initialize'
    from /Applications/Vagrant/bin/../embedded/gems/gems/vagrant-1.5.0/bin/vagrant:138:in `new'
    from /Applications/Vagrant/bin/../embedded/gems/gems/vagrant-1.5.0/bin/vagrant:138:in `<main>'
logiclabs commented 10 years ago

Me too. Exactly the same error on Windows with Vagrant 1.5 and Vagrant-Chef-Zero 0.6.0

c10l commented 10 years ago

This is how it was fixed by @sneal on Vagrant::Butcher :)

sonnysideup commented 10 years ago

any movement here? this is still busted.

jeitnier commented 10 years ago

Having the same issues with this using Vagrant 1.5.4

gavares commented 10 years ago

Updated: My problem was actually that I didn't have vagrant-berkshelf 2.0.1 installed as I thought.

vagrant plugin list

showed that I actually had version 1.3.7 (or something) installed.

Fixed the issue with:

vagrant plugin uninstall vagrant-berkshelf
vagrant plugin install vagrant-berkshelf --plugin-version=2.0.1
eashman commented 10 years ago

Same problem as gavares --

It seems like this happens if you install the vagrant-omnibus plugin AFTER you install the vagrant-berkshelf (i.e. it seems to downgrade the version of vagrant-berkshelf). I'll post elsewhere about this but just in case it bites people here.

Had to manually uninstall vagrant-berkshelf and reinstall for this to work.

galtenberg commented 10 years ago

Thanks @eashman and @gavares, this got me past a 2-hour hurdle. Also had to fully uninstall Vagrant and start over (before hitting this issue for the 2nd time), as my previous Vagrant install was pre-1.5.

eashman commented 10 years ago

FYI - I cross-posted here and there's some more info:

https://github.com/schisamo/vagrant-omnibus/issues/76

pwelch commented 10 years ago

@gavares Thanks for your update :+1:. Your solution fixed my problem as well.

ZirconCode commented 10 years ago

@gavares another thanks, saved much worry.

wsmidt commented 10 years ago

@gavares thanks! :)

bioball commented 10 years ago

@gavares Thanks!!

andrewhavens commented 10 years ago

This issue has been resolved since vagrant-chef-zero 0.7.0, so this issue can be marked as closed.