1233487 - Ansible error on vagrant provision

Status: RESOLVED FIXED

(developer.mozilla.org Graveyard :: Setup / Install, defect)

Description

[Stephanie Hobson [:shobson]]

Traceback:
==> developer-local: Running provisioner: ansible...
PYTHONUNBUFFERED=1 ANSIBLE_HOST_KEY_CHECKING=false ANSIBLE_FORCE_COLOR=true ANSIBLE_SSH_ARGS='-o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o ForwardAgent=yes -o ControlMaster=auto -o ControlPersist=60s' ansible-playbook --user=vagrant --connection=ssh --timeout=30 --limit='developer-local' --inventory-file=/Users/shobson/Public/Sites/kuma/.vagrant/provisioners/ansible/inventory --sudo -vvvv provisioning/vagrant.yml
ERROR: environment is not a legal parameter at this level in an Ansible Playbook
Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

I get this on master on my first provision after a vagrant destroy.

Comment 1

[Jannis Leidel [:jezdez]]

:shobson I opened https://github.com/mozilla/kuma/pull/3717 and I know this doesn't really *fix* fix your issue, but it seems as if I missed the fact that https://github.com/mozilla/kuma/pull/3709 used a feature that was only added in Ansible 1.9.x. So the best bet is to update Ansible and ask our contributors to do so, too. Sorry for your troubles :(

Comment 2

[Jannis Leidel [:jezdez]]

If anyone sees this issue as well, update Ansible by running:

- brew update
- brew upgrade ansible

..or whatever your package manager would allow you to update Ansible to 1.9.x.

Comment 3

[MDN Team (:mdn-dev)]

Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/8dda414294ea543b60819ef2796002f1652358d7
Fix Bug 1233487 - Specified the version of Ansible that is needed at the moment.

https://github.com/mozilla/kuma/commit/186a20e1e58827318e09db17def422a5e16b195a
Merge pull request #3717 from mozilla/bug1233487

Fix Bug 1233487 - Specified the version of Ansible that is needed at the moment.