From 6646565db9b09f8df28f436535eabfae1ffb9844 Mon Sep 17 00:00:00 2001 From: Guillaume Abrioux Date: Tue, 4 May 2021 11:42:15 +0200 Subject: [PATCH] update: fix ceph-crash stop task This is a workaround for an issue in ansible. When trying to stop/mask/disable this service in one task, the stop didn't actually happen, the task doesn't fail but for some reason the container is still present and running. Then the task starting the service in the role ceph-crash fails because it can't start the container since it's already running with the same name. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1955393 Signed-off-by: Guillaume Abrioux (cherry picked from commit 3db1ea7ec41475243559beff50b7011773c021e5) (cherry picked from commit 2d59f4579b57564b41579de530f70d86404b0201) --- infrastructure-playbooks/rolling_update.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/infrastructure-playbooks/rolling_update.yml b/infrastructure-playbooks/rolling_update.yml index b51b312d38..b85706ff40 100644 --- a/infrastructure-playbooks/rolling_update.yml +++ b/infrastructure-playbooks/rolling_update.yml @@ -880,6 +880,12 @@ systemd: name: "{{ 'ceph-crash@' + ansible_facts['hostname'] if containerized_deployment | bool else 'ceph-crash.service' }}" state: stopped + daemon_reload: yes + + # it needs to be done in a separate task otherwise the stop just before doesn't work. + - name: mask and disable the ceph-crash service + systemd: + name: "{{ 'ceph-crash@' + ansible_facts['hostname'] if containerized_deployment | bool else 'ceph-crash.service' }}" enabled: no masked: yes