Last modified: 2014-05-23 05:58:00 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T66720, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 64720 - Ruby error: "undefined method `new' for nil:NilClass (NoMethodError)" when running vagrant
Ruby error: "undefined method `new' for nil:NilClass (NoMethodError)" when ru...
Status: RESOLVED WONTFIX
Product: MediaWiki-Vagrant
Classification: Unclassified
General (Other open bugs)
unspecified
PC Linux
: Unprioritized normal
: ---
Assigned To: Ori Livneh
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2014-05-01 21:46 UTC by mvolz
Modified: 2014-05-23 05:58 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description mvolz 2014-05-01 21:46:01 UTC 
I've located the commit causing the breakage to here:

https://git.wikimedia.org/commit/mediawiki%2Fvagrant/75ecb6d38db1249e9bb98f3a20ce6ca37217bdf7

Prior to that commit vagrant works. After that commit, I get the following error when issuing any vagrant command:

>>vagrant help

/opt/vagrant/embedded/gems/gems/vagrant-1.5.0/plugins/kernel_v2/config/vm_provisioner.rb:63:in `add_config': undefined method `new' for nil:NilClass (NoMethodError)
	from /opt/vagrant/embedded/gems/gems/vagrant-1.5.0/plugins/kernel_v2/config/vm.rb:268:in `provision'
	from /home/marielle/Code/vagrant/Vagrantfile:171:in `block in <top (required)>'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/config/v2/loader.rb:37:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/config/v2/loader.rb:37:in `load'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/config/loader.rb:104:in `block (2 levels) in load'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/config/loader.rb:98:in `each'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/config/loader.rb:98:in `block in load'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/config/loader.rb:95:in `each'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/config/loader.rb:95:in `load'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/vagrantfile.rb:28:in `initialize'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/environment.rb:482:in `new'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/environment.rb:482:in `vagrantfile'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/environment.rb:313:in `host'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/environment.rb:164:in `block in action_runner'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/action/runner.rb:36:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/action/runner.rb:36:in `run'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/environment.rb:300:in `hook'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/environment.rb:144:in `initialize'
	from /opt/vagrant/bin/../embedded/gems/gems/vagrant-1.5.0/bin/vagrant:138:in `new'
	from /opt/vagrant/bin/../embedded/gems/gems/vagrant-1.5.0/bin/vagrant:138:in `<main>'
Comment 1 mvolz 2014-05-23 05:58:00 UTC 
Caused by outdated installation of vagrant
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links