All service clients methods return their response wrapped in
ResponseBody, ResponseBodyData or ResponseBodyList.
But object storage service clients were left out of this
because response from object storage APIs are not same way other
service return. Some APIs return is as string etc.
This commit makes bulk_middleware_client to return ResponseBodyData
object with consistency to other service clients.
This is step to move these clients to lib.
Partially implements blueprint consistent-service-method-names
Change-Id: Iade0a1afd0e28ea42f12df175f55eadb1bea7071
My freshly created tox pep8 py3 venv was started
to complaining about the line endings:
'H903 Windows style line endings not allowed in code'
I decided to make him happy and remove the '\r'.
Change-Id: Ifbee4a88f2f91e51cb710469316c8fcf00b00eb3
test_boot_server_from_encrypted_volume_luks is expected to use
the same feature flag as the other volume encryption tests.
The encryption can be disabled also when the system does not
have suitable keymgr.
Change-Id: I4216a002e22a2392417d9f7d3055c8cdad4a9600
Clients.py inits the orchestration client and defines and attribute
in the client manager for it. The only known consumers of attribute
are Tempest itself in the cleanup service and Murano.
I proposed a patch to Murano: Ic6fef4b4f260d13efd7b035bc012369f0da55602
The aim is to make clients stable for plugins, and I don't want the
Heat client to be in the stable interface since it's not something
that we will be supporting on Tempest side: all the Heat config
values are deprecated and will be removed during Queens.
Depends-on: Ic6fef4b4f260d13efd7b035bc012369f0da55602
Change-Id: I9f4703296a44e741cab8db6b52ba410b7dd3bed6
The test_create_server module creates a server and then it runs
multiple checks in different tests. This is done for DiskConfig
AUTO and MANUAL.
The two multinic tests however create their own server, so they
should not belong to the same class. With the current setup we
run them twice, once per DiskConfig value, which uses gate time
and resources for no clear purpose.
To fix this I'm moving these two multi nic tests to a dedicated
module.
Change-Id: I97dd4b5c703d41d9084e6e049144e4df4e3fb75d
this test will verify whether or not the catalog that it is run
against uses approved names for the services it contains. This
patch will include a few additions:
- a minimal client which will "GET" and return the service catalog,
- unit testing for the new client
- and a test that will make sure that the service catalog uses a
naming scheme that is compatible with the established governance-
approved naming scheme.
Change-Id: Ia745dff050f35cc5a3fc3744d58c6fe1e875e56f
Since there are several tests that create volume snapshot and there is
a potential to use it in other future tests, I think it's better to create
a generic method that create a volume snapshot and responsible to delete
it at the end of the test.
Change-Id: Ia78a067d6b4b729bfcc0c40d51206db6f9c4c331
This is a start to have tempest handle Cinder API versions
based on what is actually enabled. There are currently a
lot of places in the code the assume v1 and v2 are available,
but those versions may be disabled, especially as we try to
get everyone moved onto the latest (final?) v3 API version.
There are more areas that should be fixed up before we can
actually just work with v3 only, but this is a start to get
there.
Closes-bug: #1703044
Change-Id: Icc2e12f06c3b4899f934f000e191552f4a5cd2a9
An instance action event's finish_time and result can be None when
the event is not yet completed. This is common in Nova. The nova-api
service creates the instance action record and the nova-compute service
has a method which performs the actual operation on the server
instance. The method in the compute is wrapped with an EventReporter
decorator which records the event start and finish times. So until
the event (operation) is complete, the event finish_time and result
are going to be None.
Change-Id: I964d9170ca7f038e9ab968e119f03fbe9efae588
Closes-Bug: #1702758
_create_service in test_endpoint_groups.py is a class
method, so cls should be used instead of self.
Change-Id: I80e1c4ac1091d8ce98967e9e184ef63466b51990
This commit adds a flag to generate a tempest plugin list. In a local
environment, we don't need to generate a tempest plugin list, always
when we just need to see the other documents. Besides, generating the
tempest plugin list takes a long time. When GENERATE_TEMPEST_PLUGIN_LIST
environment variable is 'true'(default), the plugin list is created.
When the other value such as 'false' is specified, it isn't.
Change-Id: I6fd3cb3045ba8bbfb39c597413e13faa3cd24ae3
It will help to catch tempest plugin config and dependency issues
with tempest.
sh ./tools/tools/tempest-plugin-sanity.sh or
tox -e plugin-sanity-check will invoke the same.
Change-Id: If42561bfc1d6dcffbb6537634d7769ef90fab21d
This patch adds 'params' argument to list_backups API in v2 BackupsClient,
to enable passing additional information in the query string of the HTTP
request.
Change-Id: I8e31a55741f9bebf7b3d70491e2353b466dce06e
This patch supplements unit tests for volume v2 transfers client,
and also makes some modifications to the original unit tests.
Change-Id: Ib60665c1819ed19fdd13454bec3642ec1451b3e9
Partially Implements: blueprint tempest-lib-missing-test-coverage
This patch:
- adds ``disable_log_reason`` and ``update_forced_down`` API
endpoints to the compute ``services_client``
- adds corresponding unit tests and schemas
(for 2.11 microversion)
- changes ``host_name`` parameter in the unit tests for
``services_client`` to ``host`` because ``host_name``
is wrong; see [0] for example
However, this patch does not add API tests for these endpoints
because they result in compute services being forced down
or disabled, which are dangerous to test in the gates.
Valid use cases for these APIs include:
- negative testing
- RBAC testing (forcing a BadRequest but ensuring policy enforcement
happens beforehand)
[0] https://developer.openstack.org/api-ref/compute/#update-forced-down
Change-Id: I641218e104bba55e3679a7111e7f3d042ad7665b
