Got this and it seems that at least the syntax is not complaining anymore 
but got the following errors.. I feel like I am close

fatal: [192.168.1.161]: FAILED! => {"msg": "privilege output closed while 
waiting for password prompt:\nsu: Sorry\n"}

This is the current setup

---
- name: Install test 1
  hosts: all
  become: true
  become_method: su
  pre_tasks:
    - debug: msg=' pre roles'
    - local_action:
        command ansible-galaxy install -r requirements.yml -p .

  vars:

  tasks:
    - name: Including roles
      include_role:
name: role1

On Friday, March 20, 2020 at 4:54:54 PM UTC+1, Matt Martz wrote:
>
> `include_role` is a task, as such it must go under `tasks:`
>
> On Fri, Mar 20, 2020 at 10:50 AM Johanna Galarza <[email protected] 
> <javascript:>> wrote:
>
>> so did that I had this error: 
>> ERROR! 'include_role' is not a valid attribute for a Play
>>
>>
>> On Friday, March 20, 2020 at 4:20:33 PM UTC+1, Matt Martz wrote:
>>>
>>> Playbooks are parsed all at once, and roles which are "static", are 
>>> merged into the play at parsing time.  They are required to exist before 
>>> the playbook runs.  You could however switch to `include_role`, which loads 
>>> the role when that "task" is encountered.
>>>
>>> On Fri, Mar 20, 2020 at 10:17 AM Johanna Galarza <[email protected]> 
>>> wrote:
>>>
>>>> This is my current setup
>>>> ---
>>>> - hosts: all
>>>>   pre-tasks:
>>>>     - local_action:
>>>>         command ansible-galaxy install -r requirements.yml -p . (this 
>>>> install roles roleA, roleB, roleC)
>>>> roles:
>>>> - role1
>>>> - role2
>>>>
>>>> I have always an error message that it says that role1 doesn't exist... 
>>>> and I cannot see the first command being executed even with a debug 
>>>> message 
>>>> - so I have the feeling it is always executing roles first and then 
>>>> pre-tasks, however, I read that pre-task will be run first.... why does 
>>>> this doesn't apply here? 
>>>>
>>>> Any idea?
>>>>
>>>> -- 
>>>> 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 [email protected].
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/ansible-project/884e2977-1bdc-480b-a434-cf820b456815%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/ansible-project/884e2977-1bdc-480b-a434-cf820b456815%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>
>>>
>>> -- 
>>> Matt Martz
>>> @sivel
>>> sivel.net
>>>
>> -- 
>> 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 [email protected] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/ansible-project/217bb7e0-8269-4c03-a6ae-a073db79b367%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/ansible-project/217bb7e0-8269-4c03-a6ae-a073db79b367%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
>
> -- 
> Matt Martz
> @sivel
> sivel.net
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/a78308c7-628f-45b8-81a7-f246b5d17c35%40googlegroups.com.

Reply via email to