Error After Upgrade to Vagrant 2.3.6

The following error occurs after upgrading Vagrant to 2.3.6. It is probably a good idea to stay on 2.3.5 for the time being until this is addressed. I have run both of the following commands try to fix the problem with the plugin:

vagrant plugin update

Did not fix

vagrant plugin expunge --reinstall

Did not fix

Error message:

% vagrant up                        
Bringing machine 'default' up with 'digital_ocean' provider...
/opt/vagrant/embedded/gems/gems/i18n-1.13.0/lib/i18n.rb:210:in `translate': wrong number of arguments (given 2, expected 0..1) (ArgumentError)
	from /Users/username/.vagrant.d/gems/3.1.4/gems/vagrant-digitalocean-0.9.5/lib/vagrant-digitalocean/actions/setup_key.rb:26:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/warden.rb:48:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/warden.rb:127:in `block in finalize_action'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/warden.rb:48:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/builder.rb:180:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/runner.rb:101:in `block in run'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/util/busy.rb:19:in `busy'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/runner.rb:101:in `run'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/builtin/call.rb:53:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/warden.rb:48:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/warden.rb:48:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/builder.rb:180:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/runner.rb:101:in `block in run'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/util/busy.rb:19:in `busy'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/runner.rb:101:in `run'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/machine.rb:248:in `action_raw'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/machine.rb:217:in `block in action'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/environment.rb:631:in `lock'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/machine.rb:203:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/machine.rb:203:in `action'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/batch_action.rb:86:in `block (2 levels) in run'

What is your operating system? Try running sudo rm -Rf ~/.vagrant.d/gems/ && sudo rm ~/.vagrant.d/plugins.json

macOS 13.4. Removing all of that did not fix the issue. Take a look at the first line of the error.

These are the lines which are causing the error.

vagrant-digitalocean/lib/vagrant-digitalocean/actions/setup_key.rb

Lines 26 to 28 in adf683e

    
           env[:ui].info I18n.t('vagrant_digital_ocean.info.using_key', { 
        
             :name => ssh_key_name 
        
           })

And here is the method being called there.

https://github.com/ruby-i18n/i18n/blob/a5a2ba6c6991cf66f733016aea91edd1f0ea1113/lib/i18n.rb#L210-L225

@seth-reeser This looks to be a fix for the bug.

https://discuss.hashicorp.com/t/vagrant-digital-ocean-plugin-broken-with-2-3-6/54132/2

https://www.ruby-lang.org/en/news/2019/12/12/separation-of-positional-and-keyword-arguments-in-ruby-3-0/

Can you get this fixed up, or should I test that and make a PR?

We will patch this and release a new version. Stay tuned.

This needs the fix above in a few places. I've found and remedied them all for my use case. l can work up a pull request.

@lamech Nice work. Thanks!

This was fixed by the above referenced PR.

	env[:ui].info I18n.t('vagrant_digital_ocean.info.using_key', {
	:name => ssh_key_name
	})