# Issue with community.general.make module

**URL:** <https://forum.ansible.com/t/issue-with-community-general-make-module/38095>\
**Category:** Ansible Project\
**Tags:** rhel\
**Created:** [June 13, 2023, 1:14pm UTC](https://forum.ansible.com/t/issue-with-community-general-make-module/38095 "2023-06-13T13:14:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![harry\_devine](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/harry_devine/32/5293_2.png) [@harry\_devine](https://forum.ansible.com/u/harry_devine)\
**Post date:** [June 13, 2023, 1:14pm UTC](https://forum.ansible.com/t/issue-with-community-general-make-module/38095/1 "2023-06-13T13:14:27Z")

</div>

I have a RHEL 7 server that is running Apache Guacamole. I had a playbook that we turned into a role that’s part of an internal collection that used to work, but since I have switched it to use community.general.make instead of the old make module, the compile using make stopped working.

Here’s the call in the role/task:

- name: Install | Compiling Guacamole Server # noqa 503  
community.general.make:  
chdir: “{{ guacamole\_src\_dir + ‘/guacamole-server-’ + guacamole\_version }}”  
register: \_guacamole\_server\_compiled  
when: \_guacamole\_config\_server\_build[‘changed’]

And when that play is executed, I get the following error:

Traceback (most recent call last):  
File “/home/sdsuser/.ansible/tmp/ansible-tmp-1686592847.1340995-385-86720942975452/AnsiballZ\_make.py”, line 107, in   
\_ansiballz\_main()  
File “/home/sdsuser/.ansible/tmp/ansible-tmp-1686592847.1340995-385-86720942975452/AnsiballZ\_make.py”, line 99, in \_ansiballz\_main  
invoke\_module(zipped\_mod, temp\_path, ANSIBALLZ\_PARAMS)  
File “/home/sdsuser/.ansible/tmp/ansible-tmp-1686592847.1340995-385-86720942975452/AnsiballZ\_make.py”, line 48, in invoke\_module  
run\_name=‘ **main** ’, alter\_sys=True)  
File “/usr/lib64/python2.7/runpy.py”, line 176, in run\_module  
fname, loader, pkg\_name)  
File “/usr/lib64/python2.7/runpy.py”, line 82, in \_run\_module\_code  
mod\_name, mod\_fname, mod\_loader, pkg\_name)  
File “/usr/lib64/python2.7/runpy.py”, line 72, in \_run\_code  
exec code in run\_globals  
File “/tmp/ansible\_community.general.make\_payload\_ZqrE8r/ansible\_community.general.make\_payload.zip/ansible\_collections/community/general/plugins/modules/make.py”, line 233, in   
File “/tmp/ansible\_community.general.make\_payload\_ZqrE8r/ansible\_community.general.make\_payload.zip/ansible\_collections/community/general/plugins/modules/make.py”, line 228, in main  
File “/usr/lib64/python2.7/pipes.py”, line 269, in quote  
for c in file:  
TypeError: ‘NoneType’ object is not iterable

Any thoughts on what could be wrong?

Thanks,  
Harry

---

<div class="post-metadata">

**Author:** ![Nico\_Kadel-Garcia](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/nico_kadel-garcia/32/9998_2.png) [@Nico\_Kadel-Garcia](https://forum.ansible.com/u/Nico_Kadel-Garcia)\
**Post date:** [June 19, 2023, 11:18pm UTC](https://forum.ansible.com/t/issue-with-community-general-make-module/38095/2 "2023-06-19T23:18:36Z")

</div>

> I have a RHEL 7 server that is running Apache Guacamole. I had a playbook that we turned into a role that's part of an internal collection that used to work, but since I have switched it to use community.general.make instead of the old make module, the compile using make stopped working.

You've a few different issues. One is that you \*need\* python 3 to run  
contemporary versions of ansible. Another is that ansible went through  
a very confusing split a few years back. If you're installing ansible  
on the RHEL 7 server itself, you need to \*not\* use the old, published  
"ansible" package, which predates the split, and use a contemporary  
"ansible-core" setup.

Unfortunately, the new ansible is called "ansible-core", and the  
package called "ansible" now isn't. It's a ginormous bundle of more  
than 100 third party modules, installed as "ansible\_collections", and  
should have been labeled "ansible\_collections. No one publishes  
ansible-core as an RPM for RHEL less than RHEL 8. I used to,  
personally,

To get a more contempory version of ansible running on RHEL 7:

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;sudo yum install python3 python3-pip  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;pip3 install --user ansible-core  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ansible --version

It won't be ideal, the python3 on RHEL 7 is increasingly out of date,  
and the assemblage of dependencies for ansible-core continues to grow,  
so more and more stuff winds up in $HOME/.local/ . I used to publish  
RPM building tools for RHEL 7, but gave up when ansible-core started  
require python 3.11 for current releases.

Nico Kadel-Garcia