Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ansible Playbook has errors in Test #102

Open
benrfairless opened this issue Oct 7, 2018 · 1 comment
Open

Ansible Playbook has errors in Test #102

benrfairless opened this issue Oct 7, 2018 · 1 comment
Labels

Comments

@benrfairless
Copy link
Member

While working on #99 I get this error when trying to bring up postgresql.test

MacBook-Pro:infrastructure benfairless$ vagrant provision postgresql.test
==> postgresql.test: [vagrant-hostsupdater] Checking for host entries
==> postgresql.test: [vagrant-hostsupdater]   found entry for: 192.168.10.18 postgresql.test
==> postgresql.test: [vagrant-hostsupdater]   found entry for: 192.168.10.18 test.postgresql.test
==> postgresql.test: [vagrant-hostsupdater]   found entry for: 192.168.10.18 www.postgresql.test
==> postgresql.test: [vagrant-hostsupdater]   found entry for: 192.168.10.18 www.test.postgresql.test
==> postgresql.test: [vagrant-hostsupdater]   found entry for: 192.168.10.18 api.postgresql.test
==> postgresql.test: Running provisioner: ansible...
Vagrant has automatically selected the compatibility mode '2.0'
according to the Ansible version installed (2.7.0).

Alternatively, the compatibility mode can be specified in your Vagrantfile:
https://www.vagrantup.com/docs/provisioning/ansible_common.html#compatibility_mode

    postgresql.test: Running ansible-playbook...
PYTHONUNBUFFERED=1 ANSIBLE_FORCE_COLOR=true ANSIBLE_HOST_KEY_CHECKING=false ANSIBLE_SSH_ARGS='-o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o ControlMaster=auto -o ControlPersist=60s' ansible-playbook --connection=ssh --timeout=30 --limit="postgresql.test" --inventory-file=/Users/benfairless/code/infrastructure/.vagrant/provisioners/ansible/inventory -vv site.yml
ansible-playbook 2.7.0
  config file = /Users/benfairless/code/infrastructure/ansible.cfg
  configured module search path = [u'/Users/benfairless/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /Library/Python/2.7/site-packages/ansible
  executable location = /usr/local/bin/ansible-playbook
  python version = 2.7.10 (default, Aug 17 2018, 17:41:52) [GCC 4.2.1 Compatible Apple LLVM 10.0.0 (clang-1000.0.42)]
Using /Users/benfairless/code/infrastructure/ansible.cfg as config file
ERROR! 'creates' is not a valid attribute for a Task

The error appears to have been in '/Users/benfairless/code/infrastructure/roles/internal/awslogs/tasks/main.yml': line 14, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:


- name: Install awslogs agent
  ^ here

This error can be suppressed as a warning using the "invalid_task_attribute_failed" configuration
Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

I haven't had this issue until today, and I can't see why I would be getting this. This happens on both the master and the dev branches.

@mlandauer
Copy link
Member

This is most likely related to #106

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants