Files identified in the description:

• lib/ansible/modules/utilities/logic/import_tasks.py

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

Hi,

In my environments this issue appears using Ansible version 2.8.2, 2.8.7, 2.9.1.

In Ansible 2.6.5 is working correctly, the handler is executed correctly:

RUNNING HANDLER [iot.mongodb : restart mongodb service] *******************************************************************************
Running systemd
...

Using the other versions:

RUNNING HANDLER [iot.mongodb : restart mongodb service] *******************************************************************************
task path: ...roles/iot.mongodb/handlers/main.yml:2
skipping: [mongo-02] => {
    "changed": false, 
    "skip_reason": "Conditional result was False"
}

I try to use: import_tasks, include_tasks, etc, without no luck.

I've been trying to find a workaround but I haven't got it.

When will this bug be fixed? It's very important. I cannot use ansible branch master in production.

Regards,
Cesar Jorge

@cesarjorgemartinez It seems like you may be having a different issue. There isn't different behavior on 2.6.5 using the reproducer in this ticket. Adding this feature would be a significant change to how imports/includes fundamentally work and would probably need to go through the proposal process if it was something we wanted to add.

Then, I create a new issue? Exist multiple issues related with handler execution, and this is the closest one I've found

@cesarjorgemartinez Yes, create a new issue with a simple reproducer for the behavior you're seeing. From the brief excerpt it looks like you're having a problem with the conditional on your handler rather than a problem with notify being ignored.

I don't see a conditional in above handler...
And would expect the notify to trigger a handler if any of the imported tasks changed.

I don't see a conditional in above handler...
And would expect the notify to trigger a handler if any of the imported tasks changed.

imports do not work like tasks, and they do not have an association between the import_tasks task and the tasks within the imported file really. import_tasks is a pre-processing trigger, that is handled during playbook parsing time. When the parser encounters it, the tasks within are retrieved, and inserted where the import_tasks task was located. There is a proposal to "taskify" includes at ansible/proposals#136 but I don't see that being implemented any time soon.

Files identified in the description:

• lib/ansible/modules/import_tasks.py

If these files are incorrect, please update the component name section of the description or use the !component bot command.

click here for bot help

The one thing that always bugs me the most when using Ansible is the fact that Ansible fails to report errors when doing something that is not supported. Over the years, Ansible could have saved us a lot of headaches if it would just fail early (or report something at all) if the playbook contains unsupported constructs.

There was some effort recently to make options on some statements like this report warnings or errors instead of being silently ignored. I would not be opposed to adding this as well to avoid confusion in the future.