# Thoughts on bugfix in ActionBase.\_low\_level\_execute\_command

**URL:** <https://forum.ansible.com/t/thoughts-on-bugfix-in-actionbase-low-level-execute-command/32421>\
**Category:** Ansible Developer\
**Created:** [March 9, 2020, 2:58pm UTC](https://forum.ansible.com/t/thoughts-on-bugfix-in-actionbase-low-level-execute-command/32421 "2020-03-09T14:58:38Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rjwagner.dba](https://avatars.discourse-cdn.com/v4/letter/r/e8c25b/32.png) [@rjwagner.dba](https://forum.ansible.com/u/rjwagner.dba)\
**Post date:** [March 9, 2020, 2:58pm UTC](https://forum.ansible.com/t/thoughts-on-bugfix-in-actionbase-low-level-execute-command/32421/1 "2020-03-09T14:58:38Z")

</div>

Hey all - Last week, I opened [https://github.com/ansible/ansible/issues/68054](https://github.com/ansible/ansible/issues/68054) (raw plugin doesn’t honor executable in Ansible 2.8+). Matt proposed an update to ActionBase.\_low\_level\_execute\_command that fixes the issue. Since ActionBase is used by pretty much every Ansible module, I initially shied away from working on a PR for this bug. But after looking through the code, I’m beginning to think his change is quite low risk. The only module that passes executable into \_low\_level\_execute\_command is raw, so making his change should only affect raw. Do you all agree? If so, I’d be willing to contribute a PR, but I’ll probably need some guidance on testing this change. Would we need to test every module, or only raw?

Rob