Created
March 12, 2012 05:58
-
-
Save rtyler/2020146 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
-> % vagrant status | |
/home/tyler/.rvm/gems/ruby-1.9.3-p0@infra-puppet/gems/vagrant-1.0.0/lib/vagrant/driver/virtualbox.rb:26:in `initialize': wrong number of arguments (0 for 1) (ArgumentError) | |
from /home/tyler/.rvm/gems/ruby-1.9.3-p0@infra-puppet/gems/vagrant-1.0.0/lib/vagrant/vm.rb:136:in `new' | |
from /home/tyler/.rvm/gems/ruby-1.9.3-p0@infra-puppet/gems/vagrant-1.0.0/lib/vagrant/vm.rb:136:in `rescue in reload!' | |
from /home/tyler/.rvm/gems/ruby-1.9.3-p0@infra-puppet/gems/vagrant-1.0.0/lib/vagrant/vm.rb:128:in `reload!' | |
from /home/tyler/.rvm/gems/ruby-1.9.3-p0@infra-puppet/gems/vagrant-1.0.0/lib/vagrant/vm.rb:35:in `initialize' | |
from /home/tyler/.rvm/gems/ruby-1.9.3-p0@infra-puppet/gems/vagrant-1.0.0/lib/vagrant/environment.rb:430:in `new' | |
from /home/tyler/.rvm/gems/ruby-1.9.3-p0@infra-puppet/gems/vagrant-1.0.0/lib/vagrant/environment.rb:430:in `block in load_vms!' | |
from /home/tyler/.rvm/gems/ruby-1.9.3-p0@infra-puppet/gems/vagrant-1.0.0/lib/vagrant/environment.rb:429:in `each' | |
from /home/tyler/.rvm/gems/ruby-1.9.3-p0@infra-puppet/gems/vagrant-1.0.0/lib/vagrant/environment.rb:429:in `load_vms!' | |
from /home/tyler/.rvm/gems/ruby-1.9.3-p0@infra-puppet/gems/vagrant-1.0.0/lib/vagrant/environment.rb:121:in `vms' | |
from /home/tyler/.rvm/gems/ruby-1.9.3-p0@infra-puppet/gems/vagrant-1.0.0/lib/vagrant/environment.rb:154:in `multivm?' | |
from /home/tyler/.rvm/gems/ruby-1.9.3-p0@infra-puppet/gems/vagrant-1.0.0/lib/vagrant/environment.rb:129:in `vms_ordered' | |
from /home/tyler/.rvm/gems/ruby-1.9.3-p0@infra-puppet/gems/vagrant-1.0.0/lib/vagrant/command/base.rb:91:in `with_target_vms' | |
from /home/tyler/.rvm/gems/ruby-1.9.3-p0@infra-puppet/gems/vagrant-1.0.0/lib/vagrant/command/status.rb:19:in `execute' | |
from /home/tyler/.rvm/gems/ruby-1.9.3-p0@infra-puppet/gems/vagrant-1.0.0/lib/vagrant/cli.rb:38:in `execute' | |
from /home/tyler/.rvm/gems/ruby-1.9.3-p0@infra-puppet/gems/vagrant-1.0.0/lib/vagrant/environment.rb:163:in `cli' | |
from /home/tyler/.rvm/gems/ruby-1.9.3-p0@infra-puppet/gems/vagrant-1.0.0/bin/vagrant:43:in `<top (required)>' | |
from /home/tyler/.rvm/gems/ruby-1.9.3-p0@infra-puppet/bin/vagrant:19:in `load' | |
from /home/tyler/.rvm/gems/ruby-1.9.3-p0@infra-puppet/bin/vagrant:19:in `<main>' | |
tyler@kiwi 10:58:27 ~/source/github/infra-puppet [master *] ‹ruby-1.9.3@infra-puppet› |
Should be fixed in Bagrant 1.0.1 which I believe @mitchellh should have released this morning.
👍 Just hit this error, and found this gist, and 1.0.1 does indeed resolve the issue
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have the exact same stacktrace. Did you find out what causes this?
edit: 1fd4cb1a4e211ed5eb9127ed0c6b64a4f67ddafc of vagrant fixes this.