In extension: this command: [changed for reasons of obscurity]
*ap --vault-password-file=.vault.pw -t ktb -l MAS-01* Is being run while standing my Ansible source dir where the .vault.pw file is also placed, so why does the reading of that file fail, when it can be decrypted and read just fine using the "ansible-vault..." command? And thx the for the replies BTW. This is a bit of a head-scratcher, because it should "just work" as I see it. On Wednesday, March 31, 2021 at 11:36:24 AM UTC+2 Jacob Olsen wrote: > @ej Yes, "--vault-password-file" is being used. I'm not manually > supplying/managing Vault passwords and the playbook is being run from the > same dir as always. > > @Lars Absolutely nothing has been changed by conscious action from my > side. I just suddenly got hit by this after having used the same Playbook > (the exact same command) 200+ times. I use "--vault-password-file" in the > run-command. > > > On Tuesday, March 30, 2021 at 11:47:46 PM UTC+2 ej wrote: > >> 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. >>>> >>> -- This email, its contents and attachments contain information from J2 Global, Inc. and/or its affiliates which may be privileged, confidential or otherwise protected from disclosure. The information is intended to be for the addressee(s) only. If you are not an addressee, any disclosure, copy, distribution or use of the contents of this message is prohibited. If you have received this email in error, please notify the sender by reply email and delete the original message and any copies. -- 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/6949b63b-c367-462c-9062-53ebb562a38bn%40googlegroups.com.
