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 68e44e4cd6a7b0ee59c56f76f5312888745f81b4..2a32b52154dd3b6fd5b4607fddacf55e9260b72d 100644 (file)
--- 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: