| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |\ \ \ \ \ \ \
| |/ / / / / /
|/| / / / / /
| |/ / / / / |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
`jsonschema.draft4_format_checker` and also `jsonschema.FormatChecker.cls_checks`
are deprecated and DeprecationWarning appears every time so these make
logs a little dirty and also these attribute/classmethod will be removed
in the future.
Therefore `jsonschema.draft4_format_checker` should be replaced with
`jsonschema.Draft4Validator.FORMAT_CHECKER` and
`jsonschema.FormatChecker.cls_checks` should be replaced with
`jsonschema.Draft4Validator.FORMAT_CHECKER.checks`.
Eventually, DeprecationWarning for jsonschema will disappear with this
proposed fix.
Closes-Bug: #2008490
Change-Id: I1ef326b8ac17f4bbcbc718d13223da156b0e5ec3
|
| |\ \ \ \ \ \ |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
To releas a new tag for Tempest 2023.1, we modified the
compatible constraint in tox.ini
- https://review.opendev.org/c/openstack/tempest/+/874359/1
As new tag is released now so we can switch back to the master
constraint in tox.ini.
Change-Id: I60f38bef843ad16a54b1fc818ad2c2bcb6095a84
|
| |\ \ \ \ \ \ \
| |/ / / / / / |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
We are going to release Tempest new tag to declare the start of
support for stable/2023.1. So that new tag use stable/2023.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 2023.1 contstraint for
compatibility instead master.
These need to be move back to master constraint once release is done.
Change-Id: Iedaca324ab239cdb102b28f0eb40a9d160d1591f
|
| |\ \ \ \ \ \ \
| |/ / / / / / |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Change-Id: I11996f06bd17cdce4ee2313e4604474591c466a5
|
| |\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This will give us some data on whether or not these memory reduction
techniques help or hurt, before we roll them out to any gating jobs
for projects.
Change-Id: Ib9235d2ef93dae5c6b699d2b7141087d2bb09f46
Depends-On: https://review.opendev.org/c/openstack/devstack/+/873646
|
| |\ \ \ \ \ \ \
| |_|/ / / / /
|/| | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
We have project_reader credentials in tempest and they
use the same project as member role creds. Nova support
the project reader role in get server API. Moving the
server tests to use project reader creds in GET server
API call.
Change-Id: Id1964ae31951dba19917110f9940bff39345cef0
|
| |\ \ \ \ \ \ \ |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This PS is to permit mac addresses that include capitals letters in the
range A-F.
Change-Id: Ib0ac54848cec9c7ae315614e61cbfb4d663fcce4
|
| |\ \ \ \ \ \ \ \
| | |/ / / / / /
| |/| | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
We have a bug in dynamic creds creation where project creds
with different roles are created under a new projects. Creds
of different role of projects must be created within the same
project.
Fixing the creation of 'project_admin', 'project_member',
'project_reader', 'primary' creds in same projects. All the alt
creds will be created under same projects. but main and alt creds
will use different project, for example, 'project_alt_member'
and 'project_member' creds will be created in different project.
'admin' creds will continue be in new project as many test
use it as legacy admin.
Closes-Bug: #1964509
Change-Id: I9af005e2900195c42ecbbf7434facae2d3952f30
|
| |\ \ \ \ \ \ \ \
| |_|_|_|_|_|_|/
|/| | | | | | | |
|
| | | |_|/ / / /
| |/| | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Adding a few missing periodic jobs to experimental
queue so that we can run then on demand also.
Change-Id: Ice57829388d379e53811186a2e3c3ebb9feebaa6
|
| |\ \ \ \ \ \ \ |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Adding a documentation entry for the recently created multinode
attribute.
Change-Id: I082cce3a88a6ae88d6c671204155595c917ac08a
|
| |\ \ \ \ \ \ \ \ |
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Live migration downtime is configured as an integer option while
a default value is set to a float number. When a user tries to
override the option with another float number he receives a ValueError.
This patch changes the option to allow overriding with a float
number.
Change-Id: I955f4ec09c9a2fbaed61a82839ac15d3eef29ab0
|
| |\ \ \ \ \ \ \ \ \ |
|
| | | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
When we attach a volume to a server we are going to delete later, we
set ourselves up for having to wait for a graceful detach of that
volume from the server, which is what the API provides. That should
always work, but if the guest has crashed or become unstable, we may
end up waiting for it until we timeout and fail, even though the
end goal is to just delete the server right after. So, this adds a
flag to attach_volume() that effectively says "let this be cleaned up
when the server is deleted." We still make the detach call, but we do
not wait for it to complete. This allows nova to force things during
the server delete process and avoid us getting hung up.
Further, since deleting the server is an asynchronous operation which
returns to the API caller immediately, we could race to delete the
volume before nova has finished server delete, making it available for
deletion. So, this also changes our create_volume() cleanup to use a
special routine that checks to see if the volume is attached and if it
is, waits for it to become available before attempting to delete the
volume.
This bites us in the gate quite a bit, in the force-snapshot-on-live-
instances test scenario, which is what the referenced gate bug is
about.
Change-Id: I027789668d7d9aebcd0418d9a45801771f1eccbd
Related-Bug: #1939108
|
| |\ \ \ \ \ \ \ \ \ \
| |/ / / / / / / / / |
|
| | | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
This changes the order in which we create our test server and our test
volume in test_snapshot_create_delete_with_volume_in_use() to better
enable us to allow server deletion to detach the volume without hanging
on the guest.
Change-Id: Ia40ddacc5d5de3a57d19c4d60a65ba9bdc7c943d
Related-Bug: #1939108
|
| |\ \ \ \ \ \ \ \ \ \
| |/ / / / / / / / / |
|
| | | |_|_|_|_|_|_|/
| |/| | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
If we timeout waiting for delete attachment to complete, we should
log the guest console to see if it has crashed or has other error
messages that might indicate the reason.
Related-Bug: #1939108
Change-Id: If0ce1b7eb2064a7b91d2e426836c76171bfdff79
|
| |\ \ \ \ \ \ \ \ \
| |_|_|_|_|/ / / /
|/| | | | | | | | |
|
| | | |_|_|/ / / /
| |/| | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The test was added as part of [1]. It should succeed
when downtime is within the limit but it fails as below even
if downtime is not higher than the allowed limit:-
AssertionError: 5.0 not less than 5 : Downtime \
of 5.0 seconds is higher than expected '5'
Fix it by using assertLessEqual so it fails only
if downtime is higher than the allowed limit.
[1] https://review.opendev.org/c/openstack/tempest/+/828686
Change-Id: I1bf87bd33aecf004d9cb650110f06454584f600c
|
| | |/ / / / / /
|/| | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
tempest-full-py3 job started using the new tox env
'integrated-full' which is not present in old
tempest used in stable/ussuri to wallaby. This
commit preapre a separate job definiton for stable
ussuri to wallaby which use 'full' tox env.
Closes-Bug: #2007986
Depends-On: https://review.opendev.org/c/openstack/devstack/+/874625
Change-Id: I5f1c4de0e7ec0cc6d7f6ba7d7aa78aabc931d23e
|
| |\ \ \ \ \ \ \
| |_|/ / / / /
|/| | | | | | |
|
| | |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This generalizes the retry loop recently added (in haste) and applies
it to another set of tests that do image location updates.
Fixes-Bug: #1999800
Change-Id: Ib6a44a608cc3b6346c4b9fe23c986cb23d11a906
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
openstacksdk-functional-devstack job is broken on victoria branch as
well, and the fix [1] cannot be released as Victoria is in Extended
Maintenance already. This patch removes the job from the integrated
job template as a workaround.
[1] https://review.opendev.org/872341
Change-Id: Ib971757c0b00ebdf859231430d41ef010a7f5d79
|
| |\ \ \ \ \ \
| |_|_|/ / /
|/| | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Enable br-int-flows and br-ex-tcpdump services in
tempest-multinode-full-py3 job, these will help in
debugging network issues.
Related-Bug: #1998916
Change-Id: I947a6e2a88d7ad38cc00aa694438cb3101030168
|
| |\ \ \ \ \ \
| |_|_|_|/ /
|/| | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This reverts commit 517563fde84fa84199f13fb984945b897bf50bee.
Reason for revert: we did few improvement in job/tests run, let's see if timeout is solved or less frequent.
Change-Id: Ib29fb6d817b801e1472fc22fe761a2309f473dc0
|
| |\ \ \ \ \ \
| |/ / / / / |
|
| | | |_|/ /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Recently we are seeing a lot of job timeout(bug#2004780)
and we see many tests taking time and also number of tests
increasing over time. This is to prepare the list of extra tests
(here extra tests means the tests which are covered by the other
API or scenario tests) which we do not need to run in every
integrated jobs. Instead, we can run them in a separete job(s).
Currently I am adding admin (except keystone) and negative tests
in the 'extra tests' list but we can add more tests here which
we think are covered in some other tests.
As negative tests are important for interop, adding those extra
tests coverage for stable branch job also but running them in
periodic run only.
Related-Bug: #2004780
Change-Id: Id02221df0d6180519751c63e890851bd59fdafa0
|
| |\ \ \ \ \
| |/ / / /
| | / / /
| |/ / /
|/| | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
multinode job run all the tests including multinode and
non multinode tests. But we do not need to run all the
non multinode tests in this job instead smoke tests along
with multinode tests should be enough to run. This make
multinode jobs to run only smoke and multinode tests. For
that, we need to tag the multinode tests with 'multinode' attr.
Relavant-Bug: #2004780
Change-Id: I7e87d1db3ef3a00b3d27f0904d0af6a270e03837
|
| |\ \ \ \
| |/ / / |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
tempest-slow-py3 job run all the slow test serially which
takes lot of time and end up job timeout. This preparing
tempest-slow-parallel job which will run slow tests parallelly
in periodic run. Based on the results, later we can make
tempest-slow-py3 job to run tests in parallel.
Also, run tempest-full-parallel in periodic and based on the
result we can run tempest-full-py3 job scenario tests in parallel.
Relavant-Bug: #2004780
Change-Id: I876dacb40daa384cddc8faae3200cd3d39506ddc
|
| |\ \ \ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Depends-On: https://review.opendev.org/c/openstack/placement/+/865618
Change-Id: I1ada80cd1b63d2f446b9c284cc7354adae6774f5
|
| |\ \ \ \ \
| |_|/ / /
|/| | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When I converted this from a decorator to a context manager, I didn't
remove the fn parameter, nor was it even doing the thing I expected
on the second and later iterations because it doesn't fail in my local
environment. Apparently we're not running this test in
the tempest gate, so this adds to experimental so we can at least
run it on command.
Change-Id: Ia72b50f7f7bf64fe0ddd3f1a415b1807ff264b66
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We have a few jobs running gate even they are non voting
and run in periodic as well. They do not need to run in
every change but running/checking them in periodic run
is enough coverage. Below are the jobs moving to periodic:
* tempest-full-py3-ipv6
We do run tempest-ipv6-only job as voting in gate to
cover the ipv6 run and tempest-full-py3-ipv6 job can
run perdiocially to test the full tempest on ipv6.
*tempest-full-centos-9-stream
we already discussed and agreed in TC also that centos stream
testing is best effort and can be in periodic or non voting.
*tempest-full-test-account-no-admin-py3
Checking if tempest can be run without admin in periodic and not
on every change is enough.
* tempest-full-yoga
We do run all supported stable branch jobs periodically and running only
latest and oldest supported in check pipeline should be enough to catch
any breaking change on stable branches.
Relavant-Bug: #2004780
Change-Id: I8a2da7288e3f2264ce3cc39115c1d807b21fff95
|
