weareinteractive/ansible-ufw

ERROR! couldn't resolve module/action 'community.general.ufw'

mf69 opened this issue · 10 comments

mf69 commented

I'm getting this after installing the galaxy role just now.

ERROR! couldn't resolve module/action 'community.general.ufw'. This often indicates a misspelling, missing collection, or incorrect module path.

The error appears to be in '/home/mdf/.ansible/roles/weareinteractive.ufw/tasks/service.yml': line 3, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:


- name: Configuring service state
  ^ here

My ansible is v2.95 on Ubuntu Focal

Are you using Ansible >= 2.10 as stated in the README?
If you're version is lower, use the 1.x releases.

mf69 commented

As stated in my original message, I am using v2.95.
Is that not >= 2.10?

mf69 commented

actually I'm wrong it's 2.9.6. I will upgrade my ansible now.
Thanks.

hello, a query did you find the solution?
ERROR! couldn't resolve module/action 'community.general.ufw'

@ysmaelferradas you need to update you ansible version if you want to use the lastest version of this role.

Hey guys, what could be a problem on Ansible 2.10?
image

@kbcz1989 check your ansible version: ansible --version

the actual problem was that community.general collection was not installed:
ansible-galaxy collection install community.general

FWIW installing the community.general using:

ansible-galaxy collection install community.general

was only required on a ansible 2.9.27 and not on ansible [core 2.13.7].

FTR I had the error. EEs are a new concept to me: it turned out collections are loaded from a Docker container rather from the local filesystem, as it was the case with ansible-playbook. For now my workaround is to install collections into ./collections (as documented here: ansible-galaxy collections install community.general -p ./collections) but I'll probably end up building an EE.