"test_list_migrations_in_flavor_resize_situation" to indicate the failing request on timeout.

This is one of those tests that for some reason or the other fail randomly on our CI systems. Problem is, that the error message it fails with is not very helpful, as it just indicates that a timeout happened but not much else. This change seeks to fix that by including the request id that led to the timeout. This way, once the test fails on a build, it will be possible to search the log files for this request and track the underlying problem.

Closes-Bug: #2009701
Change-Id: Ic1ffd62f9d6ed0d69467f678c1820cddbb1fda12

This extends the recent theme of making sure the tearDown process does
not hang and ultimately fail the test because it cannot detach a
volume from a guest. We see (and have been seeing for a long time)
the live migration tests specifically fail in this way in the gate.

Change-Id: Ib1065c146ab2f927c23fc8a0b73d7040516a19a6
Related-Bug: #199232

In some deployments when Nova Compute configured together with Ironic
service there are many test_live_migration.* tests failed with an
error "Migration pre-check error: Unable to migrate...". This change
fix the issue removing '*-ironic' hosts (used in Kolla-Ansible).
The other deployments (OpenStack-Ansible, TripleO, etc.) should
deploy the Ironic-Complute services with correct hostnames.

Change-Id: I47993d16b86671433a64c6db57d53c2d15f8a7ae
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>

We are trying to make server SSH-able before detach volume
is performed (details in bug mentioned below). Creating
router and dhcp is needed to setup the proper network path
for server otherwise it fail
- https://zuul.opendev.org/t/openstack/build/04e11a0eac12447f8a3c47fb385b0753

Related-Bug: #1960346

Change-Id: I18eff5a4216d5683a5d49ad0e400ac663650e7a9

To stabilize test_resize_server_with_multiattached_volume we need to
wait for the guest OS to fully boot after the resize and before the test
attempts to detach the volume.

Closes-Bug #1960346

Change-Id: I85ee21868c9281d081c491ee590fe1457f5aa997

Continuing the work to bandaid any tests that involve volume
attachment/detachment, make the setUp() method of
ServerActionsTestJSON wait for the SSHABLE status. Some of its tests,
for example test_rebuild_server_with_volume_attached, use a
class-level server resource that is created by setUp(). We also need
to add the optional wait_until kwarg to recreate_server(), as the
latter is called by setUp() in some cases.

Change-Id: I3b7bcadbb7d608d705754b6ad7e2869e07b81b75
Related-Bug: 1960310

This will be required by the new wait_until={PINGABLE|SSHABLE} logic
within the module so move this down from
tempest.api.compute.base.BaseV2ComputeTest.

A version of this is also present in tempest.scenario.manager however
unifying that with this version is left for another change.

Change-Id: Iddfdf48da58320844e265fb1209e25a53d501f93

For Compute microversion 2.64:
1. change policies to policy in:
   * GET /os-server-groups
   * POST /os-server-groups
   * GET /os-server-groups/{server_group_id}
2. add rules in:
   * GET /os-server-groups
   * POST /os-server-groups
   * GET /os-server-groups/{server_group_id}
3. remove metadata from:
   * GET /os-server-groups
   * POST /os-server-groups
   * GET /os-server-groups/{server_group_id}

The testcases of create_server_group should also be modified.

Co-authored-by: Ghanshyam Mann <gmann@ghanshyammann.com>

Change-Id: I8fc37415c968eb64380b8bd66b713aa6b733578f

API microversion fixture is used to set the API
microversion on service client and reset it back
after test execution. That is done in setUp()
method and due to that API microversion is not
set on service client during resource_setup()
method and any API call will be requested on base
version.

To sync the complete test execution of test class
with requested API microversion, this commit moves
the API microversion setting in resource_setup()
method.

Closes-Bug: #1881863

Change-Id: Ia4b884a79cc0e50057dd57090737332bd76da37e