Snippet for hosted engine hosts shutdown:

        - name: Shutdown of HE hosts
          command: >-
            ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no
            -i /etc/pki/ovirt-engine/keys/engine_id_rsa -p {{ item.ssh.port }}
            -t root@{{ item.address }} '{{ he_shutdown_cmd }}'
          async: 1000
          poll: 0
          with_items:
            - "{{ he_hosts }}"

where the he_shutdown_cmd var is defined as:

        he_shutdown_cmd: >-
          while hosted-engine --vm-status | grep "\"vm\": \"up\"" >/dev/null;
          do sleep 5;
          done;
          sanlock client shutdown -f 1;
          shutdown -h now

Snippet for the Engine VM shutdown

        - name: Shutdown engine host/VM
          command: shutdown -h now
          async: 1000
          poll: 0

Could it be useful to insert the /usr/share/glusterfs/scripts/stop-all-gluster-processes.sh command, as suggested by Strahil, after the sanlock one, in case of GlusterFS domain?

Also one further note:

inside the role it is used the ovirt_host_facts module. I get this when I use it and debug its content:

            {
                "msg": "The 'ovirt_host_facts' module has been renamed to 'ovirt_host_info', and the renamed one no longer returns ansible_facts",
                "version": "2.13"
            }

So perhaps it should be considered to change and use ovirt_host_info instead? Any plan?

Thanks for reading.

Gianluca