nova/gate
Lee Yarwood e7cd8b49e2 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

NOTE(lyarwood): The following change is squashed here to allow both to
pass the gate without encoutering additional failures.

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
(cherry picked from commit 1e16b3184d)

Related-Bug: #1813789
Change-Id: I8af2ad741ca08c3d88efb9aa817c4d1470491a23
(cherry picked from commit b097959c1c)
(cherry picked from commit 91d410b92f)
2020-03-23 10:22:33 +00:00
..
README move gate hooks to gate/ 2017-01-04 11:05:16 +00:00
post_test_hook.sh Remove redundant call to get/create default security group 2019-11-05 23:39:10 +00:00
test_evacuate.sh nova-live-migration: Ensure subnode is fenced during evacuation testing 2020-03-23 10:22:33 +00:00

README

These are hooks to be used by the OpenStack infra test system. These scripts
may be called by certain jobs at important times to do extra testing, setup,
etc. They are really only relevant within the scope of the OpenStack infra
system and are not expected to be useful to anyone else.