| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
We are going to release a new tempest tag 31.1.0 cut an
intermediate release during the Zed development cycle to
make bug fixes available for plugins and other consumers.
Change-Id: Iebd6d6412537959e3e59bf899c3670601733cef3
|
| |\ \
| |/
|/| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
the client's _parse_body helper strips out the top
level key allowing us to miss bugs associated with
any key changes from the server [1]. Allow for opt-in
verification of the key.
[1] https://bugs.launchpad.net/manila/+bug/1968069
Change-Id: I3f17b54090c8a8e93269bd691768688242b7f010
Related-Bug: #1968069
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We merged a broken test case in Icdb3398061d0274fec8b4e10d955a4b00edf4524
as nova-live-migration job was non voting and we missed that the job
failed on the patch.
Let's make the job voting to avoid this in the future.
Change-Id: Ibe8c439da6c1ab6657b6f2618c3a72a074e24305
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Adding to the schema for volume show and creation:
- volume_type_id microverion 3.64
- encryption_key_id microverion 3.64
- cluster_name microverion 3.61
- volume_type_id microverion 3.63
Update volume backup schema
- encryption_key_id microverion 3.64
Create files per micro version under api_schema
Copy and update micro version between files,
Update volumes_client with schema_versions_info
Update backups_client with schema_versions_info
Change-Id: Ic96c8f94945caf0e202ce7f9f069247ec0f10a11
|
| |\ \ \ \
| |_|_|/
|/| | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Current test used as a basic check for multiple services
- Changed the nova reboot to HARD in order to refresh connection for
attahced devices
- Created a volume snapshot and delete it before reboot instance
- Write data to the attached volume and read post instance reboot.
Related-Bug: #1860913
Change-Id: I4151715954b3a12e6c790836d4b7bd50c0407720
|
| |\ \ \ \
| |_|_|/
|/| | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
As the test result [1] showed we missed ImagesNegativeTestJSON when
fixed https://bugs.launchpad.net/tempest/+bug/1844568
Related-Bug: #1844568
[1] https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_7a3/846187/3/check/nova-next/7a30291/testr_results.html
Change-Id: Ibd12542ee08f5020eddafcb253a978ac50f9e53a
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Live migration tests the volume attachment and checking the
server ssh-able will help to avoid any race during attachment
operation.
Note we merged this once Icdb3398061d0274fec8b4e10d955a4b00edf4524 but
that was reverted in I005755b0e527255362923a6b4bbbba2f7c1dfbd1 as it was
broken. This patch tries to make it right the second time.
Change-Id: I898db6351e39fb4569e9fefeddf870fb8af0671c
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Continuing the work of 4fc47f68c7710ccfb67c3ad28a58e047a8b51c1a, we
missed a spot in the recreate_server() call from resource_setup().
Start passing wait_until='SSHABLE' in that call.
Change-Id: I5c6d9afa1148772537d69a2a3321fcf32ad7eea5
|
| |\ \ \ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: I63afbec5e3e5619e0ab1f0c504e56dee56ae88da
Signed-off-by: Stephen Finucane <sfinucan@redhat.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
|
| |\ \ \ \ \ \ |
|
| | | |_|/ / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The change [1] added to scheduler a list of
storage_protocols upon reception of the stats from
volume. Scheduler can handle a list of storage
protocol variants for NFS, NVMeOF, iSCSI and FC.
The test_backends_capabilities compare volume
stats from list_pools and
show_backend_capabilities without check if the
procotols are in the list. Once change [1]
standardized some storage_protocols
with a default value, list_pools will show the
standard protocol defined by the position zero
from the list, and show_backend_capabilities
will return the protocol defined by user as
backend. Even if, the protocol returned by
show_backend_capabilities are in the list of
allowed protocols the test will fail if this
protocol is not equal the default position
zero from the list.
This patch provide a check if
show_backend_capabilities returns
valid storage_protocols using the list of allowed
variants and set the preferred protocol to it.
This fix is needed for third-party CI systems that
may not be running tempest in a greenfield
environment. So while cinder change [2] fixed
drivers to report the canonical storage protocol
name, we can't assume that the drivers being
tested contain that fix.
[1]https://review.opendev.org/c/openstack/cinder/+/836069
[2]https://review.opendev.org/c/openstack/cinder/+/839063
Change-Id: I04d0eaa1f6dba16bd11052f91a3d1d0967029ea6
|
| |\ \ \ \ \ \ |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
As 3.10 is next python version we will be testing in
next cycle (after Zed), let's add it in our testing in advance.
Change-Id: I1d60c21473c7b657a3f4ad57525c4561f2cfcfd5
|
| |/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Live migration tests the volume attachment and checking the
server ssh-able will help to avoid any race during attachment
operation.
Change-Id: Icdb3398061d0274fec8b4e10d955a4b00edf4524
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Tempest 31.0.0 has been released [1].
This commit adds a new page for 31.0.0 release notes.
[1] https://review.opendev.org/c/openstack/releases/+/843039
Change-Id: I290fd71dbe295087c0f3016efb541f2965f764d0
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
openstacksdk-functional-devstack job is broken on stable/ussuri
- https://storyboard.openstack.org/#!/story/2010057
and fix is under discussion which might take time
- https://review.opendev.org/c/openstack/openstacksdk/+/843978
- http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028764.html
Until then to unblock the stable/ussuri gate, let's stop
running it on ussuri gate.
Story: 2010057
Tasks: 45501
Change-Id: Ib50191621588cc00bc360bba4630f9efb66c7d00
|
| |\ \ \ \ \ \ |
|
| | |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
We've known this would eventually be necessary for a while [1], and
way back in 2017 we started seeing SHA-1 collisions [2].
There's already a patch for Swfit from 2017[3], and this patch will
update tempest side.
[1] https://www.schneier.com/blog/archives/2012/10/when_will_we_se.html
[2] https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html
[3] https://review.opendev.org/c/openstack/swift/+/525771
Change-Id: I0e9073955604ada493ec64264c6a5932627e1138
|
| |\ \ \ \ \ \ |
|
| | |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This patch adds the ability to measure network downtime during live
migration process.
A fixture has been added to start and stop a background pinger
process and also read status from it.
The downtime measurement has 0.2 seconds granularity.
In order to reduce overall traffic the ping payload size set to
minimal value.
Change-Id: I83c6a5d49f5d4da05deb677907e5048ecdd2242b
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Our documentation showed that Victoria, Ussuri and Train are the
supported releases by tempest's master, which wasn't the case.
It also showed that tempest is compatible with python 3.6, 3.7
and 3.8. We dropped py 3.6 and 3.7 support by [1].
[1] https://review.opendev.org/c/openstack/tempest/+/843182
Closes-Bug: #1976282
Change-Id: I0ccfa824f08cbdf58f26a142dac3a0881605ef08
|
| |\ \ \ \ \ \ |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Tempest 31.0.0 is released so we can
switch back the tox constraints to master.
Change-Id: Iee98fc45e44c5795875858918b630b70e6251eed
|
| |\ \ \ \ \ \ \
| |/ / / / / / |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
We are going to release Tempest new tag 31.0.0 to declare
the end of support for stable/ussuri. Pinning constraints
in tox.ini with stable/yoga constraint because Tempest is tested
with stable/yoga and master constraints. It did not use master constraints
as master dev cycle is in progress and so does their constraints also
is in progress and keep getting modified.
Further information:
https://docs.openstack.org/tempest/latest/requirement_upper_constraint_for_tempest.html
Change-Id: Ief33c3ebb527b81ae8fbd222237ad5605fad045a
|
| |\ \ \ \ \ \ \
| |/ / / / / / |
|
| | | |/ / / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
In zed cycle, OpenStack projects and oslo lib
has dropped the py3.6 and py3.7 support
- https://governance.openstack.org/tc/reference/runtimes/zed.html
With oslo not supporting the py3.6 and py3.7, Tempest master is
failing and cannot be run on py3.6|7 env.
- https://bugs.launchpad.net/tempest/+bug/1975036
We discussed about how to solve it in ML[1] and QA meeting[2] and
decided to drop it from Tempest too. Stable branches testing from
stable/victoria to stable/yoga (currently supported branch by Tempest
master) can be tested on py3.8 or if cloud run those releases on py3.6
then Tempest can be run in virtual env with py38.
Closes-Bug: #1975036
[1] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028622.html
[2] https://meetings.opendev.org/irclogs/%23openstack-qa/%23openstack-qa.2022-05-24.log.html#t2022-05-24T15:31:51
Change-Id: Ie844887a798a006794729e733748ceaa5e06d2db
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This patch ensures test under the api.compute.admin package wait until
the VM is sshable before attaches a volume to it.
Related-Bug: #1960346
Change-Id: I5f93effa280725ea41150cd7cebdf29a40db9818
|
| |\ \ \ \ \ |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
stable/victoria is in EM state and Tempest is going to be
pinned for stable/victoria which need to modify run-tempest
role to use the constraints set by the devstack or any job.
Because of Tempest 26.1.0 and with stestr 3.0.1 (beacause of upper
constraints of stestr 3.0.1 in stable/ussuri ) which does not have
new args exclude-regex so let's fallback to old arg if new arg is
passed.
Change-Id: I9cad0ccb02ee7bef0f94a1ee40e0fa117d89b5eb
|
| |\ \ \ \ \ \
| |/ / / / / |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Tempest is going to be pinned for stable/ussuri(depends on) which
need to modify run-tempest role to use the constraints set by
the devstack or any job.
Because of Tempest 26.1.0 and with stestr 2.5.1 or 3.0.1 (beacause of upper
constraints of stestr 2.5.1 in stable/train and 3.0.1 in stable/ussuri )
which does not have new args exclude-regex so let's fallback to old arg if
new arg is passed.
Change-Id: I89ae6bd5137e57cb6ec5bc3c9edecc29489bca94
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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
|
| |\ \ \ \ \ |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
With the tempst plugin on each service side, all their
service client also moved to respective tempest plugin.
Heat orchestration_client is left in Tempest as murano_tempest_plugin
was using it. Murano_tempest_plugin should use the heat client from
heat_tempest_plugin and meanwhile they do that I have proposed to
move the Tempest orchestration_client.py to Murano side so that
this removal will not break them
This will avoid the confusion that Tempest still support heat service
client and tests in-tree.
- https://review.opendev.org/c/openstack/murano-tempest-plugin/+/842823
Change-Id: I60f3adb81407d0c6a29a8e2bdf20588b3061c526
|
| |\ \ \ \ \ \ |
|
| | | |/ / / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
If you want to restore a backup, specifying only the backup ID, you will
get a new volume. However, if you pass the volume_id argument, you are
targeting the restore of an existing volume.
The problem I am having is that restore_backup() adds a second call to
addCleanup to an existing volume and this results in a 400 HTTP error.
To fix this problem, I add a simple check when we want to use an
existing volume without calling cleanup.
Change-Id: I521f69091cdad60edfe4ed85368df5decc0a7f55
|
| | |/ / / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This marks the end of support for stable/victoria
which is EM now[1]. This remove the stable/victoria
jobs and also adds relesenote to mark the end of
support of Victoria.
[1] https://releases.openstack.org/
Change-Id: Ia63cdc682a32a2bcfd748f924368db6028b64d8c
|
