This has been fixed in Vagrant 1.7.3 :) Le lundi 1 juin 2015 20:49:26 UTC+2, _debo a écrit : > > Aaaaand, spot on again. I was so sure I did upgrade my other laptop too > and instead it's still stuck on 1.6.3. I'm going to upgrade right now and > wait for the next patch release. > > Thanks again. > > On Monday, 1 June 2015 13:11:30 UTC+1, Gilles Cornu wrote: >> >> Gotcha, now I rembember of this bug. >> >> I fixed it in >> https://github.com/mitchellh/vagrant/blob/gildegoma/2103-ansible-local/plugins/provisioners/ansible/provisioner/base.rb >> >> >> But missed to port it to master branch 😕. >> I'll fix it for 1.7.3, thanks for reporting it. Note are you sûre that >> the less verbose machine is not running vagrant <= 1.6.x? > >
-- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/135c363e-bc04-4cde-80c6-cd849245bf07%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
