Comment 1 for bug 1903979

Looks like libvirtd restarted allowing the negative evacuation test to result in an ACTIVE instance on the controller. The current task stops the following service and associated sockets:

roles/run-evacuate-hook/tasks/main.yaml

   34 - name: Stop libvirtd on "{{ inventory_hostname }}"
   35 become: true
   36 systemd:
   37 ¦ name: "{{ item }}"
   38 ¦ state: stopped
   39 with_items:
   40 ¦ - libvirtd.service
   41 ¦ - libvirtd.socket
   42 ¦ - libvirtd-admin.socket
   43 ¦ - libvirtd-ro.socket

I guess I'm missing something here?