There's no yumrepo extra module in the 2.0.0.2

91 views
Skip to first unread message

alexk...@gmail.com

unread,
Feb 8, 2016, 11:08:31 AM2/8/16
to Ansible Project
Anybody knows why that? The module exists in the repo since November 2015...

Brian Coca

unread,
Feb 8, 2016, 11:10:11 AM2/8/16
to Ansible Project
Yes, well known as it is part of the future 2.1. It was merged into
devel after the 2.0 initial release went out.

--------------
Brian Coca

David Karban

unread,
Feb 8, 2016, 11:11:47 AM2/8/16
to ansible...@googlegroups.com

Hi, look into docs, will be in ansible 2.1.0.

David

Dne 8. 2. 2016 17:08 napsal uživatel <alexk...@gmail.com>:
Anybody knows why that? The module exists in the repo since November 2015...

--
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/e0f6d5b5-416b-4ef7-a8e0-3f4a6cad405d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

alexk...@gmail.com

unread,
Feb 8, 2016, 11:35:22 AM2/8/16
to Ansible Project
Yeah, now I see that in the docs. Thanks for pointing out.

alexk...@gmail.com

unread,
Feb 8, 2016, 11:39:45 AM2/8/16
to Ansible Project
The error is confusing though, hard to determine that the module just doesn't exist:

ERROR! no action detected in task
The error appears to have been in '...roles/epel/tasks/main.yml': line 7, column 3, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:

- name: Set repo proxy
  ^ here


for the task

- name: Set repo proxy
  yumrepo
: name=epel enabled=true proxy=https://{{proxy}}

Brian Coca

unread,
Feb 8, 2016, 11:49:11 AM2/8/16
to ansible...@googlegroups.com
It is very hard to distinguish that it is a missing module as all the following look like the same error:

- No action was added to a task entry ( - name: and no module )
- The task is misspelled ( - phile: )
- The task is referencing a module that is not available: ( - idontexit: or=icannotfind/read )
- The task is missing the action name ( - local_action: path=/var/tmp/test.txt )

It is even more 'fun' when the task action is dynamic:

 - action:
     module: "{{varwithmodulename}}"

We welcome pull requests to make the message and or detection better, but I doubt that we can distinguish well between the cases above.



Reply all
Reply to author
Forward
0 new messages