ERROR! no action detected in task.

[monofonik]

I'm unable to use this module when installed via ansible-galaxy. The error suggests that my playbook doesn't recognise elasticbeanstalk_app as a valid action.

Max OS X 10.12.5, Python 2.7.10, Ansible 2.1.10.

Steps to reproduce:

Create a test project:

mkdir /tmp/bs && cd /tmp/bs

Create ansible.cfg in project folder with contents:

[defaults]
roles_path = ./plays/roles

Install elastic_beanstalk module:

$ ansible-galaxy install hsingh.elastic_beanstalk
- downloading role 'elastic_beanstalk', owned by hsingh
- downloading role from https://github.com/hsingh/ansible-elastic-beanstalk/archive/v2.0.1.tar.gz
- extracting hsingh.elastic_beanstalk to /private/tmp/bs/plays/roles/hsingh.elastic_beanstalk
- hsingh.elastic_beanstalk was installed successfully

Create playbook with contents from project README, attempt to run playbook:

$ ansible-playbook test.yml 
 [WARNING]: Host file not found: /etc/ansible/hosts

 [WARNING]: provided hosts list is empty, only localhost is available

ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.

The error appears to have been in '/private/tmp/bs/test.yml': line 8, column 5, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:


  - name: Create Elastic Beanstalk application
    ^ here


The error appears to have been in '/private/tmp/bs/test.yml': line 8, column 5, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:


  - name: Create Elastic Beanstalk application
    ^ here

Any ideas?

[sidewinder12s]

I think your ansible.cfg is breaking it. The repo is setup to be cloned by galaxy and then run with ansible-playbook as is (the repo is setup for ansible to auto-discover the modules). If your setting an explicit role path it probably can't find the modules anymore.

[nijojames92]

Hi i'm having the same issue? anybody have a solution for it

[torte]

Having the same issue without setting up a custom ansible.cfg. All the actions as in the examples (elasticbeanstalk_app, elasticbeanstalk_env and elasticbeanstalk_version) are not detected.