The str to str comparison in the
test_server_connectivity_live_migration_compute uses a "<"
operation that does not work as intended. Let's fix that by using
the tempest module created for comparing string microversions.
Change-Id: Id6d18c93e8637d797404a62a23d3fcc61208fd4c
This change fixes typos in tempest code, doc, zuul yaml
and tox.ini file, which are found by codespell.
Change-Id: I8051d979e28f7dbf532181f339cbef9cd7220c76
A warning in command description of run cleanup first with dry-run
is added. The cleanup behavior is extended to allow users to delete
only resources if their name starts with a certain prefix.
Closes-Bug: #1945082
Change-Id: I65dfe051c891b3679538acec713e8616746c47f6
These were deprecated during Pike cycle[1] and multiple cycles have
passed since then.
[1] cd36841ca2
Change-Id: I15929c6f2cd472ad96a6b7086ccb8ac81ccbe7c5
This patch adds a scenario test instances with cinder volumes launches
on all available compute nodes, up to CONF.compute.min_compute_nodes.
Also 1 additional configuration is added: volume_types_for_data_volume.
Also function for create and add security group to server is moved
to tempest/scenario/manager.py to avoid code duplication.
Change-Id: I346a9505bc942e66aedad2029215617d0918a885
This patch is uploaded, since there is a bug report, while
creating a volume backup when the latest incremental backup
is deleted.
Change-Id: I2f766c1e516ce0e1c490bfc1f9d4660ad51cff86
Related-Bug: #1703011
Added test coverage to verify image is cached on remote glance
node as well.
Note: Removed potential race condtion logic where earlier we were
checking for image stays in queued state.
Depends-On: https://review.opendev.org/c/openstack/glance/+/900419
Change-Id: I866abe25e9c8204bcfb452dd2fac6181b6dfd7e0
This patch adds new class of tests, in which it is possible to
specify source and destination host to migration.
Closes-Bug: #2028540
Change-Id: If07355464d1567c18bedbf07c479e61874ec2031
The args should be passed instead of kwargs
Reason:
args contains all the parameter computed in the method
Change-Id: I80fbc5a157f7e34d3b9ba6f05b54b38d65b143be
Signed-off-by: Yosi Ben Shimon <ybenshim@redhat.com>
One can create and need to execute execute functional
tests which may operate with a different scope, i.e. without
a project name. This was not previously functional as the
tempest method would always inject a project name when
none was provided, which would then result in commands
being executed with "--os-project-name None" which would
result in the command failing.
Change-Id: Ieeed191addb277f0c39c7a11f1f77034915be7fc
Currently images created in *ImagesNegativeTest classes doesn't
use tempest prefix, just "test". This makes it hard to identify
tempest-created resources when performing cleanup. Adding prefix
to resolve the above mentioned issue.
Change-Id: Ied08c62b02e273edd5aa8a10e037eebb1f84ef85
... so that tempest can detect malformed values and give early feedback
to users.
note:
URIOpt was added in oslo.config 3.12, and the schemes argument was
added in oslo.config 3.18, so we don't have to bump the minimum version
of oslo.config from 5.2.0.
Change-Id: Ic6bddb061957bef8726a7c21e4eaa66ac471f01b
This option was deprecated some years ago[1] because it was unused.
It hasn't been used since then, too, so we can remove it now.
[1] e027ea931c
Change-Id: Id965f4b141d6ba83d4f6280f8da1475e73860cb2
Project tags API and application credentials API are default features
since Queens and we can now assume these features are available when
identity v3 API is available. Becuase queens and older releases are no
longer supported by tempest, we can drop the options to enable tests
for these features.
Also, access rules for application credentials has been a default
feature since train so we can also assume this feature is available,
because train and older releases are no longer supported.
Change-Id: I138ac02f61c5a0a22ce0d5ad2d600a09166a4764
This option was deprecated some years ago[1] because of lack of actual
implementation. RDP console is used by Hyper-V which is being retired
because WinStackers project has been retired, so no one may implement
the test cases.
[1] d5bda71259
Change-Id: I8effa01766e63645b7afb8a11dca061b3cce0334
The nova-cert service was removed from nova during Pike cycle[1] and is
no longer available since 16.0.0 release. Because Pike and older
releases are no longer supported, the option can be removed now.
[1] https://review.opendev.org/c/openstack/nova/+/459460
Change-Id: If520dc802bced4acfddd75a05a31dd83bc8c6354
This option was deprecated some years back[1], and has had no effect
since the 22.0.0 release.
[1] fd01d15d14
Change-Id: Ib2ac35eec958153e139f2fcfee05c2d6aeb56e81
This option was removed a few years ago[1], and is no longer needed
after queens EOL, according to the commit message.
[1] 48fe99faf2
Change-Id: Ia3985fcdda570c5e0cd32bdd87abfabb0ff516ac
The cinder backup tests are currently failing with the swift s3api
backend because it is invalid for S3 to have uppercase letters in a
bucket name. Use all lowercase instead.
Change-Id: Ifa2f9779af102dc1faf6488332e14aadb8d29bc0
The resource_name_prefix was introduced by [1] and in order
to allow users to fully customize the prefix of all resources
created by tempest, it needs to be used in tests.
[1] https://review.opendev.org/c/openstack/tempest/+/897231
Change-Id: I1e23d7a276b32e236fc8897d265c037773eca79d
A common pattern in some projects running tests with stestr is to
output the slowest tests from the test run after it finishes by running
'stestr slowest' after 'stestr run'.
We can do something similar in 'tempest run' with a '--slowest' option
that will run 'stestr slowest' when passed.
This addition is inspired by seeing TIMED_OUT job failures in the gate
with tests run using 'tempest run'. We could consider adding the
'--slowest' option to those command lines to make it easier to identify
the slowest tests in the job logs and potentially work on improving
their runtimes.
Change-Id: Ia88dabcb41d56d4246337ba67c140a93342ad6ab
Adding a new config option in tempest.conf as the prefix for the random
name resources with this new option all the resources created by
tempest will have the prefix defined by resource_name_prefix option
in tempest.conf. If not defined the default is tempest.
Tempest cleanup CLI will then use this config option to cleanup only the
resources that match the prefix. Make sure this prefix does not match with
the resource name you do not want Tempest cleanup CLI to delete.
This is a patch created after the conversation on
https://review.opendev.org/c/openstack/tempest/+/879923?tab=comments
Related-Bug: #1945082
Change-Id: I663a6307a5aa63299d20a304188efe6d29aea9d3
Martin Kopec