nova-live-migration: Only stop n-cpu and q-agt during evacuation testing

I8af2ad741ca08c3d88efb9aa817c4d1470491a23 started to correctly fence the
subnode ahead of evacuation testing but missed that c-vol and g-api
where also running on the host. As a result the BFV evacuation test will
fail if the volume being used is created on the c-vol backend hosted on
the subnode.

This change now avoids this by limiting the services stopped ahead of
the evacuation on the subnode to n-cpu and q-agt.

Change-Id: Ia7c317e373e4037495d379d06eda19a71412d409
Closes-Bug: #1868234
This commit is contained in:
Lee Yarwood 2020-03-20 09:19:55 +00:00
parent 53775aa819
commit 1e16b3184d
1 changed files with 2 additions and 2 deletions

View File

@ -55,8 +55,8 @@ nova boot --flavor ${flavor_id} --poll \
--nic net-id=${network_id} --availability-zone nova:${subnode} evacuate-bfv-test
# Fence the subnode
echo "Stopping all services and guest domains on subnode"
$ANSIBLE subnodes --become -f 5 -i "$WORKSPACE/inventory" -m shell -a "systemctl stop devstack@*"
echo "Stopping n-cpu, q-agt and guest domains on subnode"
$ANSIBLE subnodes --become -f 5 -i "$WORKSPACE/inventory" -m shell -a "systemctl stop devstack@n-cpu devstack@q-agt"
$ANSIBLE subnodes --become -f 5 -i "$WORKSPACE/inventory" -m shell -a "for domain in \$(virsh list --all --name); do virsh destroy \$domain; done"
echo "Forcing down the subnode so we can evacuate from it"