Hard to say with the information given. Can you add a debug task before the subversion one to confirm that the vault encrypted password is correctly decrypted:
- debug: var=secrets.svn_pass If you see its vaule is still in the encrypted form then, confirm if you are running the playbook with Vault correctly by looking at: link <http://docs.ansible.com/ansible/playbooks_vault.html#running-a-playbook-with-vault> Also, you can add -vvv to the ansible-playbook command line to get a more verbose output. e.g. ansible-playbook -vvv play.yml --ask-vault-pass On Tuesday, 31 January 2017 16:02:39 UTC, Jonty Needham wrote: > > I have the following playbook: > > --- > - > hosts: localhost > tasks: > - include_vars: > file: /path/to/my/vault/encrypted/file > name: secrets > - subversion: > repo: https://path/to/my/repo > dest: /tmp/checkout > username: username > password: secrets.svn_pass > export: yes > > > with the password file containing > > svn_pass: my_svn_password > > Yet the playbook fails with an authentication issue, but if I put the > password in in plaintext (obviously for testing!) the state passes > smoothly. What's going wrong here? > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/87278c30-b7bb-4d8f-b11c-efd403c1b62c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
