Stuck with Ansible error “couldn’t resolve module/action”? We can help you.
As part of our Server Management Services, we assist our customers with several Ansible queries.
Today, let us see how we can fix this error.
Ansible error “couldn’t resolve module/action”
Typically the error message may look as shown below:
ERROR! couldn’t resolve module/action ‘community.mysql.mysql_db’. This often indicates a misspelling, missing collection, or incorrect module path. The error appears to be in ‘/home/tech/ansible/Bobcares/test.yml’: line 4, column 7, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: tasks: – name: Create a new database with name ‘bobdata’ ^ here
Usually, the error occurred if the ansible module you have used does not exist in the built-in module of ansible. It must be a community module.
In such cases, while using the ansible-playbook command, the couldn’t resolve module message is returned.
How to resolve error “couldn’t resolve module/action”?
Today, let us see the simple steps followed by our Support Techs to resolve it.
Firstly, you can make use of ansible-galaxy to install the module.
In this case, we need to install MySQL community module.
Playbook use :
– hosts: server1.lab.com gather_facts: false tasks: – name: Create a new database with name ‘bobdata’ community.mysql.mysql_db: name: bobdata state: present
Then, the module needs to be installed in Ansible Controlle.
You can use ansible-galaxy install collection command to install the collection.
In order to do that, run the below command:
$ ansible-galaxy collection install community.mysql
You will see the below results after running the command:
$ ansible-galaxy collection install community.mysql Process install dependency map Starting collection install process Installing ‘community.mysql:2.1.0’ to ‘/home/bobcares/.ansible/collections/ansible_collections/community/mysql’
Once you install the module, you can re-run the playbook and it should run successfully.
[Still, stuck with the Ansible errors? Let us take a look into it]
In short, we saw how our Support Techs fix the Ansible error for our customers.