Comment 9 for bug 1813789

Reviewed: https://review.opendev.org/713674
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b097959c1cbc9af1d90c7502286bc3e20972201f
Submitter: Zuul
Branch: master

commit b097959c1cbc9af1d90c7502286bc3e20972201f
Author: Lee Yarwood <email address hidden>
Date: Wed Mar 18 15:17:27 2020 +0000

    nova-live-migration: Ensure subnode is fenced during evacuation testing

    As stated in the forced-down API [1]:

    > Setting a service forced down without completely fencing it will
    > likely result in the corruption of VMs on that host.

    Previously only the libvirtd service was stopped on the subnode prior to
    calling this API, allowing n-cpu, q-agt and the underlying guest domains
    to continue running on the host.

    This change now ensures all devstack services are stopped on the subnode
    and all active domains destroyed.

    It is hoped that this will resolve bug #1813789 where evacuations have
    timed out due to VIF plugging issues on the new destination host.

    [1] https://docs.openstack.org/api-ref/compute/?expanded=update-forced-down-detail#update-forced-down

    Related-Bug: #1813789
    Change-Id: I8af2ad741ca08c3d88efb9aa817c4d1470491a23