rolling_update: do not fail the playbook if nfs-ganesha is not present

The rolling update playbook was attempting to stop the
nfs-ganesha service on nodes where jewel is still installed.
The nfs-ganesha service did not exist in jewel so the task fails.

Signed-off-by: Andrew Schoen <aschoen@redhat.com>

diff --git a/infrastructure-playbooks/rolling_update.yml b/infrastructure-playbooks/rolling_update.yml
index eb2f00035e625e9df02ecd3a5cf0fb0f9f4848d0..23dfa683e44f686a29d88d5e7e4aebae9576222a 100644 (file)
--- a/infrastructure-playbooks/rolling_update.yml
+++ b/infrastructure-playbooks/rolling_update.yml
@@ -535,11 +535,15 @@
   become: True
 
   pre_tasks:
+    # failed_when: false is here so that if we upgrade
+    # from a version of ceph that does not have nfs-ganesha
+    # then this task will not fail
     - name: stop ceph nfs
       systemd:
         name: nfs-ganesha
         state: stopped
         enabled: yes
+      failed_when: false
       when:
         - not containerized_deployment