You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running version 2.0.0.2 with a backport of commit 8647fdc
Ansible Configuration:
Regression is evident with clean config.
Environment:
N/A
Summary:
The above-mentioned commit fixes become_method='sudo' with non-default shells (like /bin/csh on FreeBSD, etc.), so it is important, but it also regresses become_method='su' by incorrectly quoting commands running through "/bin/sh -c".
This change is, quite frankly, an embarrassment. I posted a fix in November, with analysis and testing on multiple platforms, but that was judged too risky to merge and in need of more testing, to the extent that it wasn't even merged into devel after the 2.0 release. And yet, here's a change that (a) once again doesn't explain what problem it's trying to solve, (b) has not only been applied to devel but backpatched into stable-2.0 immediately, and (c) after all that, is not even correct.
Issue Type:
Ansible Version:
ansible 2.0.0.2
config file = /home/lifanov/.ansible.cfg
configured module search path = /usr/local/share/ansible
Running version 2.0.0.2 with a backport of commit 8647fdc
Ansible Configuration:
Regression is evident with clean config.
Environment:
N/A
Summary:
The above-mentioned commit fixes become_method='sudo' with non-default shells (like /bin/csh on FreeBSD, etc.), so it is important, but it also regresses become_method='su' by incorrectly quoting commands running through "/bin/sh -c".
Steps To Reproduce:
Playbook:
Expected Results:
Playbook works.
Actual Results:
The text was updated successfully, but these errors were encountered: