You'll get some output that tells you where the exploded module source was written to, e.g. ANSIBLE_KEEP_REMOTE_FILES=1 ansible-playbook -vvvv deploy.yml). Run your playbook with the ANSIBLE_KEEP_REMOTE_FILES environment variable set to 1 (i.e. I do think this is a bug and apparently a test case that isn't in the unarchive test suite yet. I changed to using an absolute path and unarchive was happy. my/dest/path/my/dest/path, which didn't exist! my/dest/path, so it was effectively trying to untar into. ![]() ![]() The check that unarchive did to check if gtar would handle the file was this: /usr/local/bin/gtar -list -C. So I had the same problem and ended up debugging the unarchive module to find out why it thought it couldn't handle the file.
0 Comments
Leave a Reply. |