Tempest test_server_actions missing evacuate server test (and client)

[Felipe Monteiro]

Currently, test_server_actions does not have a test for evacuating a server [0], nor does it have an evacuate API in servers_client [1].

[0] https://developer.openstack.org/api-ref/compute/?expanded=evacuate-server-evacuate-action-detail
[1] https://github.com/openstack/tempest/blob/master/tempest/lib/services/compute/servers_client.py

Evacuate should be added to servers_client and corresponding tests should be added.

[Martin Kopec (mkopec)]

Unassigning due to a long inactivity.

[Martin Kopec (mkopec)]

API has been added to the servers_client by https://review.opendev.org/c/openstack/tempest/+/447962

Test case is still missing though.

[Lukas Piwowarski (lukas-piwowarski)]

Discussed during office hours:
https://meetings.opendev.org/meetings/qa/2023/qa.2023-11-22-17.00.log.html

[Martin Kopec (mkopec)]

The documentation states (https://docs.openstack.org/api-ref/compute/?expanded=evacuate-server-evacuate-action-detail) that:
* The failed host must be fenced and no longer running the original server.
* The failed host must be reported as down or marked as forced down using Update Forced Down.

These conditions are difficult to reproduce with 100% accuracy and that isn't a behaviour of a good test.
Also, even if we were able to replicate the pre-conditions, it would mean we can't run any other tests (in case of a setup with one compute node) plus we would risk that we won't be able to bring the host back up and that would fail the whole test run.

I'm closing this as Won't Fix (considering our current resources and all the time this has been opened). If you feel otherwise, feel free to reopen the LP. Thanks.