Are you making sure that you're using the same ansible.cfg with the value for "vault_password_file" set correctly each time you run the playbook? Since it says "no vault secrets found", it sounds like it could not be reading that value in from the config file. And just running the playbook from a different directory could cause it not to use the correct ansible.cfg.
Or are you specifying the filename containing the password using the --vault-password-file command-line option instead of using ansible.cfg? On Tuesday, March 30, 2021 at 9:13:24 AM UTC-6 [email protected] wrote: > It's worth noting, others don't get hit like that when they run the same > playbook on my behalf. Why the difference for me? > > On Tuesday, March 30, 2021 at 4:41:48 PM UTC+2 Jacob Olsen wrote: > >> G'day all, >> >> New to the group, glad to be here. To not waste too much of anyone's >> time, I will get straight to it. >> >> When I run some Ansible Playbooks, I now suddenly get this error message: >> >> [The below changed for reasons of internal security] >> >> fatal: [MAS-01]: FAILED! => {"ansible_facts": {}, >> "ansible-included-files": [], "changed": false, "message": "Attempting to >> decrypt but no vault secrets found"} >> >> I haven't changed anything anywhere, all I do is a "git pull" every >> Monday or so. When I use "ansible-vault" to read my vault secrets file >> locally, the content is decrypted and displayed just fine. >> >> Why has this suddenly started happening? I tried re-cloning my Ansible >> dir, no luck. >> >> Thx. >> >> J. >> > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/3b297129-9ff8-4f9f-9424-4857f1ef8730n%40googlegroups.com.
