Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes to fail2ban config should restart the fail2ban service #5661

Open
acozine opened this issue Dec 23, 2024 · 0 comments
Open

Changes to fail2ban config should restart the fail2ban service #5661

acozine opened this issue Dec 23, 2024 · 0 comments
Assignees
Labels

Comments

@acozine
Copy link
Contributor

acozine commented Dec 23, 2024

Expected behavior

When we push a change to our fail2ban configuration, the change should kick off ("notify" in Ansible terminology) a handler to restart the service.

Actual behavior

When we push a change to our fail2ban configuration, the task that restarts the handler does not run.

Steps to replicate

Change the fail2ban configuration in the nginxplus role, run the playbook to update it.

Impact of this bug

Changes to fail2ban configuration are not immediately applied.

Relevant links and code snippets, if applicable

We do have a restart fail2ban handler.
However, in the install-prerequisites.yml file, only one task notifies that handler.
Documentation about Ansible handlers.

Implementation notes, if any

Add notify: restart fail2ban to any task in install-prerequisites.yml that should run the handler to force a restart of the fail2ban service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants