ERROR! 'retries' is not a valid attribute for a TaskInclude

[Shifa Shaikh]

My requirement is to run the script stop-all as many times (5 retries) until the output of ps -fu user1 |wc -l becomes less than 2.

I wrote the below ansible playbook for the same:

cat stop.yml

  - hosts: dest_nodes
    tasks:
      - name: Start service
        include_tasks: "{{ playbook-dir }}/inner.yml"
        retries: 5
        delay: 4
        until: stopprocesscount.stdout is version('2', '<')

cat inner.yml

- name: Start service
  shell: ~/stop-all
  register: stopprocess


- name: Start service
  shell: ps -fu user1 |wc -l
  register: stopprocesscount

However, I get the below error running the playbook.

ERROR! 'retries' is not a valid attribute for a TaskInclude


The error appears to be in '/app/playbook/stop.yml': line 19, column 9, but may
be elsewhere in the file depending on the exact syntax problem.


The offending line appears to be:


- name: Start service
  ^ here

Can you please suggest?

[Stefan Hornburg (Racke)]

On 5/21/20 4:48 AM, Shifa Shaikh wrote:
> My requirement is to run the script stop-all as many times (5 retries) until the output of ps -fu user1 |wc -l becomes
> less than 2.
>
> I wrote the below ansible playbook for the same:
>
> cat stop.yml
>
> |
>   -hosts:dest_nodes
>     tasks:
>       -name:Startservice
>         include_tasks:"{{ playbook-dir }}/inner.yml"
>         retries:5
>         delay:4

>         until:stopprocesscount.stdout isversion('2','<')

> |
>
> cat inner.yml
>
> |
> -name:Startservice
>   shell:~/stop-all
>   register:stopprocess
>
>
> -name:Startservice
>   shell:ps -fu user1 |wc -l
>   register:stopprocesscount
> |
>
>
> However, I get the below error running the playbook.
>
> |
> ERROR!'retries'isnota valid attribute fora TaskInclude
>
>

> Theerror appears to be in'/app/playbook/stop.yml':line 19,column 9,but may
> be elsewhere inthe file depending on the exact syntax problem.

>
>
> Theoffending line appears to be:
>
>
> -name:Startservice
>   ^here
> |
>
> Can you please suggest?

The question is why you don't use one of the various mechanism on a Linux system to ensure
that a process is started or stopped.

Regards
Racke

>
> --
> 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 <mailto:ansible-proje...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/8a89923a-eebf-433a-92d7-4098c7af2b03%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/8a89923a-eebf-433a-92d7-4098c7af2b03%40googlegroups.com?utm_medium=email&utm_source=footer>.


--
Ecommerce and Linux consulting + Perl and web application programming.
Debian and Sympa administration. Provisioning with Ansible.

[Shifa Shaikh]

@Stefan Our service involves a set of processes thus, the start script invokes those several processes and hence the need to count the number of processes using `wc -l` to determine if the service (not the process) is running or not. 

[Dick Visser]

This sounds all very much like pushing a round peg into a square hole. 

I would focus on fine tuning some systemd unit files and their dependencies, instead of the carpet stopping/starting approach.

--

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 view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/4a53d56d-3e8a-4929-9cbd-b4b3d67b8237%40googlegroups.com.

--

Sent from a mobile device - please excuse the brevity, spelling and punctuation.

[Suneel Gali]

>>>> " ERROR! 'retries' is not a valid attribute for a TaskInclude"

Can we use "until" against include_tasks? 

Its like we are inserting the same tasks multiple times in the  playbook ...  

Can you use until condition with the actual task itself and check?

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAL8fbwPz1t-6KsQa%2BN9VEU937a17pk3i9AZTP%2BhONu9om_aZQQ%40mail.gmail.com.