Unwanted debug informations

42 views
Skip to first unread message

_debo

unread,
May 31, 2015, 5:26:37 PM5/31/15
to vagra...@googlegroups.com
Hey there guys, 

Just a quick question. I recently started to work with Vagrant and Ansible after many years using it with Chef. 
What caught my attention is that I get some more verbose output on one of two different, but similar machines, both running vagrant 1.7.2 and OSX 10.10. 

The one being more verbose outputs the following:

~$ vagrant provision
==> default: Running provisioner: ansible...
PYTHONUNBUFFERED=1 ANSIBLE_FORCE_COLOR=true ANSIBLE_HOST_KEY_CHECKING=false ANSIBLE_SSH_ARGS='-o UserKnownHostsFile=/dev/null -o ForwardAgent=yes -o ControlMaster=auto -o ControlPersist=60s' ansible-playbook --private-key=/Volumes/Projects/MyCompany/MyVendor/MyProject/tools/vagrant/.vagrant/machines/default/virtualbox/private_key --user=vagrant --connection=ssh --limit='all' --inventory-file=../ansible/inventories/dev --extra-vars={"private_interface":"172.16.0.2","hostname":"sandbox.dev"} ../ansible/playbook.yml

Does anyone know what's that and can I remove it? It doesn't happen on my other machine.

Thanks for your help.

Best,
Debo

Gilles Cornu

unread,
Jun 1, 2015, 7:48:36 AM6/1/15
to vagra...@googlegroups.com
Hi Debo,

Please check that the ´verbose´ option of the ansible provisioner is unset (or set to ´false´). I suppose it's not the case on the "chattier" machine.

Otherwise, do you use the VAGRANT_LOG environment variable?

Cheers,
Gilles

Gilles Cornu

unread,
Jun 1, 2015, 8:11:30 AM6/1/15
to vagra...@googlegroups.com
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?

Marco De Bortoli

unread,
Jun 1, 2015, 8:54:04 AM6/1/15
to vagra...@googlegroups.com
Hi Gilles,

I'm glad I somehow helped being a good epiphany duck :)
As per the less verbose machine I'm not sure at this point. I'll double check later today and get back to you.

Thanks again for taking time to look into this.

Cheers,
Debo

--
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+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

_debo

unread,
Jun 1, 2015, 2:49:26 PM6/1/15
to vagra...@googlegroups.com
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.

Gilles Cornu

unread,
Jul 11, 2015, 1:49:06 AM7/11/15
to vagra...@googlegroups.com
This has been fixed in Vagrant 1.7.3 :)
Reply all
Reply to author
Forward
0 new messages