A number of handlers that are run, particularly within the common role, can affect certain properties of subsequent tasks.

For example, changes made to UMASK configuration via pam_umask can produce different results depending on whether some tasks get run as part of the same playbook when the change has not yet been applied via handler, of if they are run subsequently.

This has particularly happened with some test cases where the file/directory permissions would flap between 0640 and 0644 depending on when the PAM configuration handler was run.

While this particular handler has been "fixed" in current code base, there may be other parts in the roles that require similar treatment.

The following should be done:

• Revisit all handlers and figure out if any of them should be triggered immediately in order to have properly consistent system state for subsequent tasks.
• Update role reference documentation.
• Update usage instructions.
• Update release notes.