Ansible internally fails on errors as a key design feature.

Any tasks you want to ignore would need the "ignore_errors: True" flag on
those specific tasks.

I'm sorry if you don't like how that was flagged in the stats, but we can't
change that.



On Thu, Oct 23, 2014 at 7:14 PM, Matt Madrid <[email protected]> wrote:

> Thanks James. I guess I wasn't clear. I know how to re-run tasks, but my
> question is more about how to force the playbook to continue on failure
> without using ignore_errors. I want the output of the run to show how many
> tasks succeeded and how many failed. Currently it will stop running tasks
> on a host when there's a failure.
>
> On Thursday, October 23, 2014 8:22:09 AM UTC-7, James Cammarata wrote:
>>
>> Hi Matt,
>>
>> I would recommend using tags on any tasks that you may want to re-run
>> individually, that way you can limit what is re-run. You can also use the
>> --start-at-task option for ansible-playbook to restart your playbook at a
>> later part of your plays.
>>
>>
>> On Tue, Oct 21, 2014 at 12:59 PM, Matt Madrid <[email protected]> wrote:
>>
>>> I'd like to run a playbook and have ansible continue on to the next task
>>> when a task fails. This way I get a play summary showing exactly how many
>>> tasks failed and how many succeeded and I can pick out specific tasks to
>>> re-run on specific hosts. AFAIK, the only way to do this is to use
>>> ignore_errors:true. But that's not what I want. ignore_errors causes
>>> ansible to show it as "ok" in the play summary. I actually want it to show
>>> failed but continue on to the next task. Am I missing something?
>>>
>>> Thanks,
>>>
>>> --
>>> Matt M.
>>>
>>> --
>>> 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 post to this group, send email to [email protected].
>>> To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/ansible-project/460413de-e7b8-4a03-a97d-
>>> 492d6b2a4ebc%40googlegroups.com
>>> <https://groups.google.com/d/msgid/ansible-project/460413de-e7b8-4a03-a97d-492d6b2a4ebc%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
> 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 post to this group, send email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/ebe8c45f-d634-4196-996d-cd71a32a55d8%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/ebe8c45f-d634-4196-996d-cd71a32a55d8%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CA%2BnsWgyD0MsBDXeSrrdtmHGbpb47%3DUOBUKSGHYwwUO_66gucHg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to