update: restart iscsigws daemons after upgrade

In containerized context, containers aren't stopped early in the
sequence.
It means they aren't restarted after the upgrade because the task is
just checking the daemon status is started (eg: `state: started`).

This commit also removes the task which ensure services are started
because it's already done in the role ceph-iscsigw.

Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
(cherry picked from commit c7708eb4582f65717599d2d7bee7a7a5885ecc2b)

diff --git a/infrastructure-playbooks/rolling_update.yml b/infrastructure-playbooks/rolling_update.yml
index a1ad48530c94096cc605f1e2bdb174c797c5b88b..d32e15df3221e0bf106a983af0a0acbac47cd070 100644 (file)
--- a/infrastructure-playbooks/rolling_update.yml
+++ b/infrastructure-playbooks/rolling_update.yml
@@ -906,7 +906,6 @@
         - rbd-target-api
         - rbd-target-gw
         - tcmu-runner
-      when: not containerized_deployment | bool
 
     - import_role:
         name: ceph-defaults
@@ -925,18 +924,6 @@
     - import_role:
         name: ceph-iscsi-gw
 
-    - name: start ceph iscsi services
-      systemd:
-        name: '{{ item }}'
-        state: started
-        enabled: yes
-        masked: no
-      with_items:
-        - tcmu-runner
-        - rbd-target-api
-        - rbd-target-gw
-      when: not containerized_deployment | bool
-
 
 - name: upgrade ceph client node
   vars: