Handlers and failures

Archives Ansible Project
1

Hey,

I have a play where I make edits to apache configs which includes a notify “restart apache”. That all works well, except in the following scenario:

  1. Task A changes apache configs. Task B runs after task A fails and the play aborts. Apache still runs the old version of the config file.

  2. I re-run the playbook, now task A skips since there’s nothing to change and Apache does not get restarted. The play finishes successfully but Apache never got restarted.

One path to go is to immediately restart apache, but that would lead to multiple restarts per run. Any ideas?

-Nadav

2

can you share your playbook, it is not clear the line of dependencies between A, B, and template file

3

Here’s an example of the scenario I am describing:

  • handlers:
    -name: restart apache
    -service: apache state=restarted

  • tasks:

  • name: enable apache proxy module [A]
    command; a2enmod proxy creates=/etc/apache/mods-ehabled/proxy.load
    notify: restart apache

  • name: task that may fail [B]
    command: this_may_fail

On this first run apache gets reconfigured, task B fails so apache doesn’t get restarted. On the second run, the first task is skipped, task B completes successfully, and apache does not get restarted and ends up running the original configuration.

4

I wonder if ansible's retry feature could be made smart enough to note the
handlers that were notified but not executed. Then on the subsequent run,
those handlers would get executed.

- James

5

What if you just abort the remaining tasks, and still run the handlers that have already been set on that run?

6

Currently the retry mechanism is an inventory file, so likely not.

The mechanism suggested before is a “force handlers” flag to be used with the option.

–Michael