New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unarchive task fails second time it's ran #24781
Comments
Complementing, this could be somewhat related to #17038 and as per @abadger comment (#17038 (comment)) i'm opening a new issue. |
Does it fail the same way under Python2? |
Didn't try with python 2, since this remote host only has python 3 installed. Will spin up a Vagrant vm and test with that. |
@nitzmahone didn't happen for me with python2 on the remote host. |
Hi. Today I had a similar issue. After second run of unarchive task with "list_files=True" I can't ssh into servers anymore with my deploy user. The ownership for /home/$USER is changed to the user with UID 1000. In my case from ansible:users into ubuntu:users and centos:users for centos machines. |
@abadger Thank you very much for the quick fix. |
ISSUE TYPE
COMPONENT NAME
unarchive
ANSIBLE VERSION
OS / ENVIRONMENT
Controller site: 4.4.0-78-generic #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Host: 4.4.0-1013-aws #22-Ubuntu SMP Fri Mar 31 15:41:31 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
SUMMARY
Unarchive module fails with "Error: a bytes-like object is required, not 'str'\r\n" error message, but only if the task would not be executed, because the files are already extracted on the remote host.
STEPS TO REPRODUCE
Python version on remote host is
Python 3.5.2
.Full error message:
EXPECTED RESULTS
Task should execute without errors both times.
ACTUAL RESULTS
Task fails the second time it's executed (when files already exist on the server)
Removed host name but it's ec2 instance.
The text was updated successfully, but these errors were encountered: