You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Question
This is a question about usage, and possibly style in respect of plays within a playbook.
One of the tasks in the post section of the role, is the following:
name: Flush handlers
ansible.builtin.meta: flush_handlers
This ,if I have understood the description, causes all handlers in a play that have a notify set to be actioned.. irrespective of the role in which the handler is defined. I tripped over having a user defined handler with one of the same name as in the rhel9 role ( "Restart sshd"), so it ran before the other role itself had run causing the play to fail.
Is it "good form" to run the rhel9cis role in it's own play? Is there a clean way to namespace the tasks so that they do not clash?
Environment (please complete the following information):
Ansible Version: [2.16.9]
Host Python Version: [3.11 ]
Ansible Server Python Version: [3.9]
Additional Details:
The text was updated successfully, but these errors were encountered:
Great question, As you have mentioned i would suggest the same, to run it as its own play or the order in which you run your roles.
Due to the number of changes/tasks in these roles and the way the vendors give updates, i would run these individually unless you are able to keep on top of the changes as part of your solution.
Question
This is a question about usage, and possibly style in respect of plays within a playbook.
One of the tasks in the post section of the role, is the following:
ansible.builtin.meta: flush_handlers
This ,if I have understood the description, causes all handlers in a play that have a notify set to be actioned.. irrespective of the role in which the handler is defined. I tripped over having a user defined handler with one of the same name as in the rhel9 role ( "Restart sshd"), so it ran before the other role itself had run causing the play to fail.
Is it "good form" to run the rhel9cis role in it's own play? Is there a clean way to namespace the tasks so that they do not clash?
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: