geerlingguy/ansible-vagrant-examples

awx - ansible remote provisioner: * The following settings shouldn't exist: become

laghao opened this issue · 8 comments

laghao commented

I'm having a ubuntu 16.04 machine, and have all the requirements but when I try Vagrant up the awx box I get the following error:

vagrant up
Bringing machine 'awx' up with 'virtualbox' provider...
==> awx: Box 'geerlingguy/centos7' could not be found. Attempting to find and install...
awx: Box Provider: virtualbox
awx: Box Version: >= 0
==> awx: Loading metadata for box 'geerlingguy/centos7'
awx: URL: https://vagrantcloud.com/geerlingguy/centos7
==> awx: Adding box 'geerlingguy/centos7' (v1.2.4) for provider: virtualbox
awx: Downloading: https://vagrantcloud.com/geerlingguy/boxes/centos7/versions/1.2.4/providers/virtualbox.box
==> awx: Successfully added box 'geerlingguy/centos7' (v1.2.4) for 'virtualbox'!
There are errors in the configuration of this machine. Please fix
the following errors and try again:

ansible remote provisioner:

  • The following settings shouldn't exist: become
laghao commented

Issue fixed and committed.

banzo commented

@Passpes I have a similar issue (OSX, Ansible 2.4.1 and Vagrant 2.0.1), how did you manage to fix it?

2cld commented

@banzo @Passpes Same question, and-or what commit fixed it for you?

catmini:kubespray cat$ vagrant --version
Vagrant 1.9.1
catmini:kubespray cat$ ansible --version
ansible 2.4.1.0
catmini:kubespray cat$ git log
commit 33adb334cdf133135de3c9614f743fd8a032664d (HEAD -> master, origin/master, origin/HEAD)
Author: Stanislav Makar stamak@users.noreply.github.com
Date: Sun Nov 5 10:40:41 2017 +0200

Fix openstack tenant id variable name (#1932)
geerlingguy commented

With vagrant 2.x, become should be set. I'm not sure why you're getting a failure, maybe there was a bug in Vagrant 2.0.1 or 1.9.1?

banzo commented

I just tried with Vagrant 2.0.1 and it works fine, thanks.

maksimluzik commented

Had same issue with Vagrant 1.9.7, upgraded to Vagrant 2.0.1 and it worked. I think this can be closed.

stale commented

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

stale commented

This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.