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
Fix string/binary encoding issue in pull.py #36962
Labels
affects_2.6
This issue/PR affects Ansible v2.6
bug
This issue/PR relates to a bug.
needs_info
This issue requires further information. Please answer any outstanding questions.
python3
support:core
This issue/PR relates to code supported by the Ansible Engineering Team.
Projects
Comments
Files identified in the description: If these files are inaccurate, please update the |
ansibot
added
affects_2.6
This issue/PR affects Ansible v2.6
bug
This issue/PR relates to a bug.
needs_triage
Needs a first human triage before being processed.
python3
support:core
This issue/PR relates to code supported by the Ansible Engineering Team.
labels
Mar 3, 2018
alikins
removed
the
needs_triage
Needs a first human triage before being processed.
label
Mar 5, 2018
+label affects_2.1 Yeah, no, not just 2.6. |
ansibot
added
the
needs_info
This issue requires further information. Please answer any outstanding questions.
label
Mar 19, 2018
bcoca
added a commit
to bcoca/ansible
that referenced
this issue
Mar 19, 2018
abadger
added a commit
to abadger/ansible
that referenced
this issue
Mar 19, 2018
* Fix a traceback in ansible-pull on python3 comparing output from subprocess with a text string. * Rename variables that hold byte strings so we are clear that those are not text strings. * Use to_text() to transform variable that's being displayed as it's less fragile than str(). Fixes ansible#36962
abadger
added a commit
to abadger/ansible
that referenced
this issue
Mar 20, 2018
* Fix a traceback in ansible-pull on python3 comparing output from subprocess with a text string. * Rename variables that hold byte strings so we are clear that those are not text strings. * Use to_text() to transform variable that's being displayed as it's less fragile than str(). Fixes ansible#36962 (cherry picked from commit b98ad3a)
abadger
added a commit
that referenced
this issue
Mar 20, 2018
* Fix a traceback in ansible-pull on python3 comparing output from subprocess with a text string. * Rename variables that hold byte strings so we are clear that those are not text strings. * Use to_text() to transform variable that's being displayed as it's less fragile than str(). Fixes #36962
nitzmahone
pushed a commit
that referenced
this issue
Mar 29, 2018
* Compare byte strings to byte strings * Fix a traceback in ansible-pull on python3 comparing output from subprocess with a text string. * Rename variables that hold byte strings so we are clear that those are not text strings. * Use to_text() to transform variable that's being displayed as it's less fragile than str(). Fixes #36962 (cherry picked from commit b98ad3a) * Add changelog entry for python3 ansible-pull fix
abadger
added a commit
that referenced
this issue
Mar 29, 2018
* Fix a traceback in ansible-pull on python3 comparing output from subprocess with a text string. * Rename variables that hold byte strings so we are clear that those are not text strings. * Use to_text() to transform variable that's being displayed as it's less fragile than str(). Fixes #36962 (cherry picked from commit b98ad3a)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
affects_2.6
This issue/PR affects Ansible v2.6
bug
This issue/PR relates to a bug.
needs_info
This issue requires further information. Please answer any outstanding questions.
python3
support:core
This issue/PR relates to code supported by the Ansible Engineering Team.
ISSUE TYPE
COMPONENT NAME
lib/ansible/cli/pull.py
ANSIBLE VERSION
Current
CONFIGURATION
Python 3
OS / ENVIRONMENT
Linux
SUMMARY
The value in out is always binary encoded, because it's returned that way from
run_cmd
.STEPS TO REPRODUCE
Run ansible-pull
EXTRA
Replaces #36364 - I'm closing that PR, because that bot annoys the crap out of me.
The text was updated successfully, but these errors were encountered: