# executable: /bin/bash not always respected

**URL:** <https://forum.ansible.com/t/executable-bin-bash-not-always-respected/22950>\
**Category:** Ansible Project\
**Created:** [November 2, 2016, 11:47pm UTC](https://forum.ansible.com/t/executable-bin-bash-not-always-respected/22950 "2016-11-02T23:47:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![DigitalHermit](https://avatars.discourse-cdn.com/v4/letter/d/9d8465/32.png) [@DigitalHermit](https://forum.ansible.com/u/DigitalHermit)\
**Post date:** [November 2, 2016, 11:47pm UTC](https://forum.ansible.com/t/executable-bin-bash-not-always-respected/22950/1 "2016-11-02T23:47:35Z")

</div>

Hello all:

First post here. I am a relatively new user to Ansible and find it quite powerful. Alas, I’ve run into some oddness that I haven’t been  
able to figure out.

I have a playbook here: [https://github.com/kwanlowe/ansible\_examples/blob/master/playbooks/pvFreeDisk.yml](https://github.com/kwanlowe/ansible_examples/blob/master/playbooks/pvFreeDisk.yml)

This playbook searches a host for “free” disks – i.e., ones with no partitions – and creates a new LVM partition and adds it to an existing  
volume group. I didn’t see a playbook that did exactly what I needed so cobbled together the above.

On most systems it works fine. On RHEL7/CentOS7 it does as expected. On RHEL5 it breaks with the following (reformatted for easier reading):