Ruby Error after update over the weekend on my vagrant and homestead installation

[Jessica Unger]

Hello, 

I am trying to get vagrant working. It was working fine prior to an update to my OSX this weekend, on 10.13.3. When I now try to get vagrant up in my terminal I get the following error. Any help is appreciated. I have version 2.0.3 of Vagrant installed. 

➜  Homestead git:(9f36545) ✗ vagrant up

/opt/vagrant/embedded/lib/ruby/2.4.0/psych.rb:377:in `parse': (<unknown>): did not find expected key while parsing a block mapping at line 17 column 7 (Psych::SyntaxError)

from /opt/vagrant/embedded/lib/ruby/2.4.0/psych.rb:377:in `parse_stream'

from /opt/vagrant/embedded/lib/ruby/2.4.0/psych.rb:325:in `parse'

from /opt/vagrant/embedded/lib/ruby/2.4.0/psych.rb:252:in `load'

from /Users/jessica/Homestead/Vagrantfile:28:in `block in <top (required)>'

from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/config/v2/loader.rb:37:in `load'

from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/config/loader.rb:126:in `block (2 levels) in load'

from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/config/loader.rb:119:in `each'

from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/config/loader.rb:119:in `block in load'

from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/config/loader.rb:116:in `each'

from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/config/loader.rb:116:in `load'

from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/vagrantfile.rb:28:in `initialize'

from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/environment.rb:771:in `new'

from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/environment.rb:771:in `vagrantfile'

from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/environment.rb:517:in `host'

from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/environment.rb:185:in `block in action_runner'

from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/runner.rb:33:in `run'

from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/environment.rb:504:in `hook'

from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/environment.rb:753:in `unload'

from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/bin/vagrant:154:in `ensure in <main>'

from /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/bin/vagrant:154:in `<main>'

Thanks!

[Alvaro Miranda Aguilera]

Hello

can you try with a vanilla vagrant project?

mkdir p64

cd p64

vagrant init -m hashicorp/precise64

vagrant up

does work ?

Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/d09c1039-30c4-4532-b19f-3ed8d258babf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Dan Menezes]

Did you solve the problem?