# Howto Install nmcli extras module?

**URL:** <https://forum.ansible.com/t/howto-install-nmcli-extras-module/19831>\
**Category:** Ansible Project\
**Created:** [November 23, 2015, 5:51pm UTC](https://forum.ansible.com/t/howto-install-nmcli-extras-module/19831 "2015-11-23T17:51:01Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![jdelaporte](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jdelaporte/32/366_2.png) [@jdelaporte](https://forum.ansible.com/u/jdelaporte)\
**Post date:** [November 23, 2015, 5:51pm UTC](https://forum.ansible.com/t/howto-install-nmcli-extras-module/19831/1 "2015-11-23T17:51:01Z")

</div>

Hi everyone,

I was trying to use the nmcli module this morning, and kept getting an error (ERROR: nmcli is not a legal parameter in an Ansible task or handler). Apparently, this module doesn’t ship with Ansible, as noted on the [Extras Modules page](http://docs.ansible.com/ansible/modules_extra.html). However, I don’t know how to install/configure an Extras module…can someone please enlighten me?

Thanks!  
Joanna

---

<div class="post-metadata">

**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\
**Post date:** [November 23, 2015, 6:06pm UTC](https://forum.ansible.com/t/howto-install-nmcli-extras-module/19831/2 "2015-11-23T18:06:01Z")

</div>

The extras get installed with Ansible, you don't need to do anything.

The most probable cause is that the module was added in a version  
newer than what you are using.

---

<div class="post-metadata">

**Author:** ![jdelaporte](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jdelaporte/32/366_2.png) [@jdelaporte](https://forum.ansible.com/u/jdelaporte)\
**Post date:** [November 23, 2015, 6:24pm UTC](https://forum.ansible.com/t/howto-install-nmcli-extras-module/19831/3 "2015-11-23T18:24:35Z")

</div>

I have Ansible 1.9.4, installed via pip. Everything else seems to be working fine. Even though the extras modules supposedly are included by default, I seem to have no nmcli module in my modules directory:

$ ls /usr/share/ansible/  
cloud/ messaging/ source\_control/  
commands/ monitoring/ system/  
database/ net\_infrastructure/ utilities/  
files/ network/ web\_infrastructure/  
internal/ notification/  
inventory/ packaging/

$ ls /usr/share/ansible/network/  
get\_url slurp uri

---

<div class="post-metadata">

**Author:** ![jdelaporte](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jdelaporte/32/366_2.png) [@jdelaporte](https://forum.ansible.com/u/jdelaporte)\
**Post date:** [November 23, 2015, 6:25pm UTC](https://forum.ansible.com/t/howto-install-nmcli-extras-module/19831/4 "2015-11-23T18:25:39Z")

</div>

Hi Brian,

I just noticed now it is in version 2.0. Now to find instructions for installing that version…

Thanks!  
Joanna

---

<div class="post-metadata">

**Author:** ![jdelaporte](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jdelaporte/32/366_2.png) [@jdelaporte](https://forum.ansible.com/u/jdelaporte)\
**Post date:** [November 23, 2015, 6:43pm UTC](https://forum.ansible.com/t/howto-install-nmcli-extras-module/19831/5 "2015-11-23T18:43:20Z")

</div>

After installing 2.0.0 beta 3 from a tarball, do I need to do something to reload modules or plugins?

FAILED! =\> {“failed”: true, “msg”: “ERROR! Invalid shell type specified (bash), or the plugin for that shell type is missing.”}

---

<div class="post-metadata">

**Author:** ![jdelaporte](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jdelaporte/32/366_2.png) [@jdelaporte](https://forum.ansible.com/u/jdelaporte)\
**Post date:** [November 23, 2015, 6:54pm UTC](https://forum.ansible.com/t/howto-install-nmcli-extras-module/19831/6 "2015-11-23T18:54:24Z")

</div>

I think I just needed to change /etc/ansible/ansible.cfg:

executable = /bin/bash

to

executable = /bin/sh

It is working now. I am pretty sure I needed to change that to /bin/bash for constrained sudo in the past, but I have changed how sudo is handled lately, so it might no longer be an issue.
