Conversation

Notices

1. Embed this notice
   zhenech (zhenech@chaos.social)'s status on Thursday, 07-Nov-2024 08:16:27 JST zhenech

   Days since the fact that Ansible runs handlers at the end of the play and not at the end of the role that triggered them broke shit for me: 0️⃣

   • Embed this notice
     Andreas Scherbaum (ascherbaum@mastodon.social)'s status on Thursday, 07-Nov-2024 08:16:25 JST Andreas Scherbaum

     in reply to

     @zhenech I don't get why the handler aren't forced by #Ansible at the end of the Role, logically that makes sense because the concept "encapsulated tasks in a Role" ends at the end of the Role.

     And I have "meta: flush_handlers" at the end of every role ...

   • Embed this notice
     Mauricio Teixeira 🇧🇷🇺🇲 (badnetmask@hachyderm.io)'s status on Thursday, 07-Nov-2024 08:16:25 JST Mauricio Teixeira 🇧🇷🇺🇲

     in reply to

     • Andreas Scherbaum

     @ascherbaum @zhenech
     I agree it's awful when things break, but the handler behavior is clearly documented:
     https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_handlers.html#controlling-when-handlers-run

   • Embed this notice
     Mauricio Teixeira 🇧🇷🇺🇲 (badnetmask@hachyderm.io)'s status on Thursday, 07-Nov-2024 08:18:09 JST Mauricio Teixeira 🇧🇷🇺🇲

     in reply to

     • Andreas Scherbaum

     @ascherbaum @zhenech
     Also, the handlers don't necessarily need to be defined in a role, and you can call role handlers from different roles or tasks, as long as they are in the same play. So it's an interesting behavior, but it has it's uses.

   • Embed this notice
     Andreas Scherbaum (ascherbaum@mastodon.social)'s status on Thursday, 07-Nov-2024 09:45:58 JST Andreas Scherbaum

     in reply to

     • Mauricio Teixeira 🇧🇷🇺🇲

     @badnetmask @zhenech You know, documented != useful.

     When I create a role, the intention is to wrap a certain piece of action/state in this role. Once the role execution is finished, there's nothing which prevents #Ansible from running all notified handlers.

     I get the argument about not running handlers multiple time, the counter argument is that a role which is executed later might find a situation where the service is not yet in the desired state.

   • Embed this notice
     Mauricio Teixeira 🇧🇷🇺🇲 (badnetmask@hachyderm.io)'s status on Thursday, 07-Nov-2024 09:45:58 JST Mauricio Teixeira 🇧🇷🇺🇲

     in reply to

     • Andreas Scherbaum

     @ascherbaum @zhenech
     I personally prefer that I can choose when to run in the middle of a play, rather than not having that kind of control. But yeah, it's a matter of opinion at this point.