You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
While working on #99 I get this error when trying to bring up postgresql.test
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.
The text was updated successfully, but these errors were encountered: