Issue #8391
closedcouldn't resolve module/action 'firewalld
Description
I was using the installer but failed with the error
TASK [pulp.pulp_installer.pulp_webserver : include_tasks] **************************************************************
fatal: [galaxyng.cos.devops.corp]: FAILED! => {"reason": "couldn't resolve module/action 'firewalld'. This often indicates a misspelling, missing collection, or incorrect module path.\n\nThe error appears to be in '/home/terekcampbell/.ansible/collections/ansible_collections/pulp/pulp_installer/roles/pulp_webserver/tasks/firewalld.yml': line 22, column 7, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n - name: Accept HTTP connections on port REPLACE ME WITH BELOW\n ^ here\n"}
RUNNING HANDLER [pulp.pulp_installer.pulp_common : Load the SELinux policy packages] ***********************************
RUNNING HANDLER [pulp.pulp_installer.pulp_common : Restore SELinux contexts on Pulp dirs that must exist] **************
RUNNING HANDLER [pulp.pulp_installer.pulp_common : Restore SELinux contexts on Pulp dirs that may exist] ***************
PLAY RECAP *************************************************************************************************************
Changing the 'firewalld' modules in pulp_webserver/tasks/firewalld.yml from "firewalld" to "ansible.posix.firewalld" resolved the issue.
Wanted to let you know to update the install accordingly.
Also note, the version I'm using of https://galaxy.ansible.com/pulp/pulp_installer was 3.10.0 but that wasn't available in the dropdown
Related issues
Updated by mdepaulo@redhat.com almost 4 years ago
- Is duplicate of Task #8365: As a user I have installer running with ansible 3 added
Updated by mdepaulo@redhat.com almost 4 years ago
Hi Terek,
Sorry you ran into this issue, and thank you for the suggestion on how to fix it.
We fixed this as part of the Ansible 3.0 work (also possibly Ansible 2.10 was affected).
This fix is in the new pulp_installer 3.11.0 release.
We solved it by adding:
collections:
- ansible.posix
to roles/pulp_webserver/meta/main.yml
We considered doing it your way, but thought that this way is preferable, for code clarity and for maintaining compatibility with Ansible 2.9
-Mike & Fabricio
Updated by mdepaulo@redhat.com almost 4 years ago
- Status changed from NEW to CLOSED - CURRENTRELEASE