From fd739205f8df93765b453f3efd06c2305dd97b88 Mon Sep 17 00:00:00 2001
From: Michael Vasseur <14887731+vmcj@users.noreply.github.com>
Date: Tue, 17 Sep 2024 13:25:53 +0200
Subject: [PATCH] Make sure tune_cpu gets started

In the past we could (and did) fail somewhere in the playbook which
would result in not handling this notified handler. This also meant that
we would not copy the file again on the next run, so didn't kick the
handler and also didn't hit the handler on the next run.

The disadvantage here is we might hit other handlers more often if next
roles want to hit the same handler.
---
 provision-contest/ansible/roles/judgedaemon/tasks/main.yml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/provision-contest/ansible/roles/judgedaemon/tasks/main.yml b/provision-contest/ansible/roles/judgedaemon/tasks/main.yml
index 74001b70..54a50965 100644
--- a/provision-contest/ansible/roles/judgedaemon/tasks/main.yml
+++ b/provision-contest/ansible/roles/judgedaemon/tasks/main.yml
@@ -102,6 +102,9 @@
   notify:
     - Enable and restart tune_cpu
 
+- name: Enable and restart tune_cpu (flushing here to make sure we start the service without a reload)
+  ansible.builtin.meta: flush_handlers
+
 - name: Copy judgedaemon related systemd unit files
   copy:
     remote_src: true