From: Mike Christie <mchristi@redhat.com>
Date: Thu, 9 May 2019 19:52:08 +0000 (-0500)
Subject: igw: Fix rolling update service ordering
X-Git-Tag: v3.2.16~1
X-Git-Url: http://git.apps.os.sepia.ceph.com/?a=commitdiff_plain;h=0a24078bbbb31aa15e09887a60ea40cce812b626;p=ceph-ansible.git

igw: Fix rolling update service ordering

We must stop tcmu-runner after the other rbd-target-* services
because they may need to interact with tcmu-runner during shutdown.
There is also a bug in some kernels where IO can get stuck in the
kernel and by stopping rbd-target-* first we can make sure all IO is
flushed.

Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1659611

Signed-off-by: Mike Christie <mchristi@redhat.com>
(cherry picked from commit d7ef12910e7b583fa42f84a7173a87e7c679e79e)
---

diff --git a/infrastructure-playbooks/rolling_update.yml b/infrastructure-playbooks/rolling_update.yml
index 68e44e4cd..2a32b5215 100644
--- a/infrastructure-playbooks/rolling_update.yml
+++ b/infrastructure-playbooks/rolling_update.yml
@@ -713,9 +713,9 @@
         enabled: yes
       failed_when: false
       with_items:
-        - tcmu-runner
         - rbd-target-api
         - rbd-target-gw
+        - tcmu-runner
       when: not containerized_deployment
 
   roles: