Current development cycle (2024.2) is non SLURP release and
we do not need run grenade-skip-level on non SLURP. If any
project want to run skip level upgrade testing in non SLURP
release they can use grenade-skip-level-always job (for example
Nova does).
Change-Id: I68521a4ffcac52144308f17cd1062b99630e4dd2
These were deprecated during Pike cycle[1] and multiple cycles have
passed since then.
[1] cd36841ca2
Change-Id: I15929c6f2cd472ad96a6b7086ccb8ac81ccbe7c5
To releas a new tag for Tempest 2024.1, we modified the
compatible constraint in tox.ini
- https://review.opendev.org/c/openstack/tempest/+/913950/
As new tag is released now so we can switch back to the master
constraint in tox.ini.
Change-Id: I1ec341903929f240ef3e796ee0db2acda9af9823
We are going to release Tempest new tag to declare the start of
support for stable/2024.1. So that new tag use stable/2024.1
constraint in the tox env.
For example: if anyone use Tempest new tag in future say
1 year later then tox env also should use the 2024.1 contstraint for
compatibility instead master.
Also, making ironic-tempest-bios-ipmi-direct-tinyipa as
non voting to merge his change.
These need to be reverted once release is done.
Change-Id: I5ee1ce6b3ffbbb1f47e448fc15d540f74b21684f
The job hasn't fail with the reason it was marked non-voting for,
for a while now.
Closes-Bug: #2053026
Change-Id: I035925416c9420624ea5d55b6bc5c1b08fcacf25
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
ML2/OVN is default Neutron backend in Devstack since couple of cycles
already and it would be useful to have ovs/ovn logs collected in all
such jobs.
Related-Bug: #2052787
Change-Id: Icce8f469b3bc1154b6ac46382f35ee6ff91682f3
Required to keep running jobs when branches are
renamed from stable to unmaintained.
yoga already transitioned to unmaintained. victoria,
wallaby and xena are in progress.
Related-Bug: #2056276
Change-Id: I12eac55c9864eeeed255f426c537b7e53e908521
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
The role will find out the available hosts and set
compute.migration_source_host and compute.migration_dest_host
options in tempest.conf if tempest_set_src_dest_host is set to
True.
Change-Id: Ic01970b100a7bb30d9c78229204c7de67681108c
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
Making tempest-tox-plugin-sanity-check job non-voting
until we fix this issue that makes the job constantly
failing:
https: //bugs.launchpad.net/tempest/+bug/2053026
Change-Id: I1d50b8e81425fa228e03d37a81aaaffdfa5c089c
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
We are going to release Tempest new tag 37.0.0 to declare
the end of support for stable/yoga. stable/2023.2 constraint
is latest stable constraints tested with current tempest hash
which is going to be used for 37.0.0 release.
Further information:
https://docs.openstack.org/tempest/latest/requirement_upper_constraint_for_tempest.html
Change-Id: I0b4863c219b71b75f665e7a7599063124c34b2de
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
This marks the end of support for stable/yoga
which is moving to 'unmaintained' stage[1].
This remove the stable/yoga jobs and also adds
relesenote to mark the end of support of Yoga.
[1] https://review.opendev.org/q/topic:%22yoga-unmaintained%22
Change-Id: I364bcd69f55753e4c99f66240f743e3bc7205832
tempest-all job has been timeouting for a while now, let's
increase the timeout limit to 3 hours similarly like we have set
for tempest-slow-py3. Both of the jobs run scenario tests.
Change-Id: Ia843611f052fa06e5ed540cdae070f6c2c7a0f7b
... 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