I find it surprising that unarchive's dest parameter has to be an absolute path, since that is inconsistent with the dest parameter for the git and get_url modules, for example. ![]() This issue is consistent with your analysis that only invalid arguments cause the error for you. That then get's passed along with -C to tar, causing tar to fail (silently from the Ansible user's perspective) since tar can't find the relative directory name because Ansible invokes tar from the temporary directory instead of the initial directory. ![]() It certainly didn't fix things for me this time around.Īfter a bunch more digging and hacking debug code into the Ansible source it turns out that my issue (at least this time around) was due to setting unarchive's dest parameter to a relative path. Msg: 'Failure downloading, Not a directory: ''/tmp/ansible_unarchive_payload_rdhpQ9/ansible_unarchive_payload.zip/ansible/modules/software-name_1.2.7.tar.gz'''Īfter resurecting the code I was working on when I filed this issue and setting up a machine to test against, I'm not sure why my PR fixed things for me at the time. : ok=1 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0įile "/tmp/ansible_unarchive_payload_rdhpQ9/ansible_unarchive_payload.zip/ansible/modules/unarchive.py", line 763, in mainįatal: : FAILED! => changed=false Command \"/usr/bin/unzip\" could not handle archive." Command \"/usr/bin/tar\" could not handle archive. Make sure the required command to extract the file is installed. (0, '', 'OpenSSH_8.0p1 Ubuntu-6build1, OpenSSL 1.1.1c \r\ndebug1: Reading configuration data /home/user/.ssh/config\r\ndebug1: Reading configuration data /etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line 19: Applying options for *\r\ndebug1: auto-mux: Trying existing master\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug2: mux_client_hello_exchange: master version 4\r\ndebug3: mux_client_forwards: request forwardings: 0 local, 0 remote\r\ndebug3: mux_client_request_session: entering\r\ndebug3: mux_client_request_alive: entering\r\ndebug3: mux_client_request_alive: done pid = 4076\r\ndebug3: mux_client_request_session: session request sent\r\ndebug3: mux_client_read_packet: read header failed: Broken pipe\r\ndebug2: Received exit status from master 0\r\n')įile "/tmp/ansible_unarchive_payload_YCZydn/ansible_unarchive_payload.zip/ansible/modules/files/unarchive.py", line 164, in Command \\"/usr/bin/gtar\\" could not handle archive." ![]() Command \\"/usr/bin/unzip\\" could not handle archive. ![]() "msg": "Failed to find handler for \\"/var/tmp\\". WARNING: The below traceback may *not* be related to the actual failure.įile "/tmp/ansible_unarchive_payload_A8osHn/_main_.py", line 151, in SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKe圜hecking=no -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=root -o ConnectTimeout=10 -o ControlPath=/tmp/awx_1082_gg0huk32/cp/fc89cda61c i '/bin/sh -c '"'"'rm -f -r /tmp/root/ansible/ansible-tmp-1573585522.28-175080413594493/ > /dev/null 2>&1 & sleep 0'"'"'' > ESTABLISH SSH CONNECTION FOR USER: root Failed to connect to the host via ssh: Shared connection to closed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |