npm is not a legal parameter at this level in an Ansible playbook

[ansi11]

I am trying to install forever through npm on Centos 6.3 version. Getting the error as above if my .yml file is first level of playbook.

---

- name: install forever

  npm: name=forever global=yes state=latest

If I am adding these lines in mail.yml present in tasks folder of node.js role , I am getting this error:

npm is not defined as a legal parmeter at this level in an Ansible tasks or handler. 

[Michael Peters]

Sounds like you're running ansible from a git checkout. If that is the
case, you need to make sure your git submodules have been fetched as
well since the big ansible git submodule split:

See https://groups.google.com/forum/#!msg/ansible-project/TUL_Bfmhr-E/rshKe30KdD8J

> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-proje...@googlegroups.com.
> To post to this group, send email to ansible...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/1d091a24-4fb8-4378-936e-ef6e588e452e%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Michael DeHaan]

Hi Michael,

That should not be a problem because Ansible will self-report and give a helpful error when it can't find modules this way.

ansi,

How did you install Ansible?

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAJQqANeZbmvi1%2BbMnY1ZvrWYB2j_UhwoPz9F7h2XHUmpFPXHjA%40mail.gmail.com.

[Nikita Agrawal]

Hi Michael,

I installed ansible through git checkout only. I am just checking if the problem is with git submodules. Will update shortly. 

Thanks for the reply :)

[Nikita Agrawal]

On Wednesday, October 29, 2014 11:33:41 AM UTC+5:30, Nikita Agrawal wrote:

Hi Michael,

Thanks for the reply.I installed ansible through git checkout only. I used these commands as described on http://docs.ansible.com/intro_installation.html

$ git clone git://github.com/ansible/ansible.git --recursive
$ cd ./ansible 

$ source ./hacking/env-setup 

So , I believe this is taking care of git submodules as well. But the problem still persist.

[Nikita Agrawal]

I tried running following on existing git checkout .

git submodule update --init --recursive

same issue still exist

[Michael DeHaan]

Hmm, odd.

I don't know why that would be the case.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/0e5de7e5-5bb4-4355-985b-78ad6b485ca2%40googlegroups.com.

[Nikita Agrawal]

Any second thoughts on this are welcome..