Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Ansible error couldn’t resolve module/action

by | Jul 1, 2021

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:

– 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:
gather_facts: false
– name: Create a new database with name ‘bobdata’
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.



Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.