| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
as slow test"
|
| | | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
test
We are seeing more timeout in tests (and so does sometimes it end up to
job timeout) in various jobs. A few examples are
- miltinode job
- https://zuul.openstack.org/build/084729c5a1fe46e091a17a50441e99d5/log/job-output.txt
- stable/yoga job
- https://zuul.opendev.org/t/openstack/build/9b79f54d3f6c4e05ae6619fdac7ad95a
Two tests in doubt and taking more time is
test_minimum_basic_instance_hard_reboot_after_vol_snap_deletion
- taking 258.358054s
- https://zuul.openstack.org/build/084729c5a1fe46e091a17a50441e99d5/log/job-output.txt#34173
- taking 187.411266s
- https://zuul.opendev.org/t/openstack/build/9b79f54d3f6c4e05ae6619fdac7ad95a/log/job-output.txt#25738
test_minimum_basic_scenario
- taking 309.109043s
- https://zuul.opendev.org/t/openstack/build/d068cb494d234fe7b79dc5ae6fd6ae69/log/job-output.txt#24052
marking these test as slot test and monitor if there is another slow
test we can find.
Related-Bug: #2004780
Change-Id: I0aff3507b3bf3498ab0ecd548bb57cdcd97ec11a
|
| |\ \ \ \ \ |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
In one test, we are downloading the entire image (into memory) and
re-uploading it. That works when the image is 16MiB but not when it
is 1GiB. This adds support to the internal http client for chunked
downloads (similar to upload), makes the image client able to take
that flag, and finally makes the offending test do a chunked upload/
download streaming operation.
Note this un-skips the test, effectively reverting a6b7e334c
because the test should no longer consume large amounts of memory.
Related-Bug: #2002951
Change-Id: I31e537538a1862e71091aa470da3b8e9c799bf15
|
| |\ \ \ \ \ \
| |_|_|/ / /
|/| | | | | |
|
| | | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The commit marks the job temporarily as non-voting to unblock the
CI. There are multiple patches waiting to be merged which address
other bugs (e.g. the timeout issues) and this job fails at ~50%
rate which makes the merging of other patches comlicated.
Related-Bug: #1998916
Change-Id: I4ef3a6e5c4bbef93d355bfa42589fdb60db43663
|
| |\ \ \ \ \ |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
While debugging the ``rescue`` test functionality with ironic's
tempest plugin, we discovered that if the environment suggests the
agent is available, then we may enter a situation where the test
can fail because paramiko prefers ssh over password authentication.
This is important, because for rescue functionality in particular,
it is password authentication based without the use of SSH keys,
as a temporary password is generated by the services and provided
to the user requesting to rescue the instance/node.
Instead of trying to make an assumption that password being present
means we should just disable the agent, explicitly allow the caller
to specify it.
Change-Id: Iefb6cb5cb80eb2b9a4307912c4d6d07c684ed70a
|
| | |/ / / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
If glance is unable to fetch the http image URL we give it due to
transient network problems, we currently fail the test because it
does not retry itself and we get a BadRequest. Because such problems
can happen in a CI run due to network interruptions, this adds a
retry loop on that condition when we go to add a location. If we fail
to add the location for some legit reason related to our actual
location URI or other parts of the request, all the retries will
fail and we'll still catch the problem.
Change-Id: I944eb076c9f9056200dc193b52f2004038a6942f
Related-Bug: #2004641
Related-Bug: #1999800
Related-Bug: #2006473
|
| |\ \ \ \ \ |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
With the new version of tox, the interpretation of escaping in the
command section changed [1]. For example, the `tox -e smoke` runs the
following command to execute tempest tests when tox==4.3.5. is installed:
tempest run --regex '[.*\bsmoke\b.*]'
(missing '\' in front of '[', ']') ^^
The issue can be fixed either by adding another backslash ('\\[') or
moving the regular expressions to separate variables. The first solution
won't, however, be backwards compatible with the older version of tox
therefore this patch uses the second approach.
[1] https://tox.wiki/en/latest/config.html#substitutions
Change-Id: Ie5ea7f9305c7e7611f205d2e0703849bd6321a68
|
| |\ \ \ \ \ \
| |/ / / / /
| | | | / /
| |_|_|/ /
|/| | | | |
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
With the new version of tox the parsing of postargs value has changed.
Previously an empty string was discarded by tox if it appeared in the
postargs value in contrast with the latest version of tox which
leaves the empty string intact.
The behavior of the latest tox version makes some jobs fail as some
variables in the run-tempest role have an empty string as a default
value. This leads in some cases to the execution of an incorrect tempest
command, for example:
tempest run --regex '[.*\bsmoke\b.*]' '' --concurrency=2
The patch changes the default value for blacklist_option,
exclude_list_option and tempest_test_regex variables to None to prevent
an empty string from being passed to postargs variable in tox.
Change-Id: I006e33c5ea0753b68cf1feb8580cb029209af9a8
|
| |\ \ \ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
test_dhcp_port_status_active is the only missing test in
tempest.api.network.admin.test_dhcp_agent_scheduler.
DHCPAgentSchedulersTestJSON compared to
n_t_p.api.admin.test_dhcp_agent_scheduler.DHCPAgentSchedulersTestJSON.
By moving it from n-t-p we can get rid of the whole module, reducing the
test duplications.
Change-Id: I1d6410bb0d9eed1bc1e8e503c1cada48d275a9af
|
| | |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
openstacksdk-functional-devstack job is broken on wallaby branch and
the fix [1] cannot be released as Wallaby 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: I578562e0d94d3cda4e9deb5fb44c3f674ab0628e
|
| |\ \ \ \ |
|
| | | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
stable/wallaby is in EM state and Tempest is going to be
pinned for stable/wallaby which need to modify run-tempest
role to use the constraints set by the devstack.
Change-Id: I985c222a1a461dff10ff33716fd2263a1a89813a
|
| |\ \ \ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Tempest cleanup gathers the project, user, and role id. Since
commit a857880423, this info is collected but not used. In
specific cases this method raises an error so it's better to
remove it.
Closes-bug: #2003125
Change-Id: Icd71a2962808628edb611257ac544f0277cde1f3
|
| |\ \ \ \ \ |
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
With commit [1] support for dhcpcd client was added to tempest
but there was not cleaned one of the TODO notes related to that.
So this patch simply cleans that left over.
[1] https://review.opendev.org/c/openstack/tempest/+/871270
Change-Id: I0c94ac5e7fd7b6da0fd051b9ff7d4c226be73f76
|
| |\ \ \ \ \
| |/ / / /
|/| | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In the test_port_security_macspoofing_port test, NIC on one of the vms
is set to DOWN, MAC of this NIC is changed to the spoofed one and NIC is
then bring back to UP.
For some reason it works fine in Cirros 0.5.x but not in 0.6.0 and newer
as after bringinig interface back to be UP there is also need to restore
configured previously IP addresses.
This patch adds check of IPs configured on that NIC before it is switch
to DOWN and later restores the same IPs configuration when NIC is UP
again.
Related-Bug: #2003063
Change-Id: I05d2118125195a387163ad1f0177fd9dfc916238
|
| |\ \ \ \ \
| |/ / / /
| | / / /
| |/ / /
|/| | | |
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In Cirros 0.6.0 and newer there is dhcpcd client used instead of old
udhcpc. This patch adds support to that new client in the
remote_client's renew_lease method.
Related-Bug: #2003063
Change-Id: I5d5648332e1c84221e708c29a904fcaaffdb451e
|
| |\ \ \ |
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Tempest provides a LockFixture to avoid two potentially interfering
tests to run in parallel. However, this solution does not scale when
we want to separate a set of tests from many other test cases. For
example, host aggregate and availability zone testing needs compute
hosts without any nova servers to be able to test moving computes
between aggregates but a lot of other tests are creating nova
servers. To fully separate these aggregate tests from the rest of
the tempest test cases, this patch proposes a @serial class decorator
to mark a test class to be run totally independently of any other test
classes.
Under the hood, the @serial decorator is implemented with a tempest-wide
interprocess read-write lock. The serial test classes always take the
write lock, while the non-serial classes take the read lock. The lock
allows in many readers OR a single writer. So the serial tests are run
independently from the rest.
To minimize the time a serial test blocks other tempest tests run in
parallel, this patch also introduced a serial_tests test directory to
store the serial tests. The current test ordering in a fresh env
uses alphabetical order so the serial tests will run at the end of
the execution not randomly in the middle. The gate uses fresh VMs
for every run so we can rely on this optimization there. In local
envs where tests are re-run, the subsequent runs will be ordered at
runtime by stestr. Therfore, a longer runtime might be observed due to
locking, but the correctness of the test execution is still kept.
Related-Bug: #821732
Change-Id: I0181517edab75f586464a38c4811417f888783b1
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This test causes excessive memory usage in the test executor as it
downloads glance image data in memory. This currently causes OOM issues
in the gate so the test case is skipped until the image data copying is
made smarter.
Related-Bug: #2002951
Change-Id: I0bfac0310fdd6ef44a633d40422cfcfdfc85a426
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There are functions set as classmethod while used in testcase
The cleanup done on class level and not part of the testcase
The problem is that we may see testcase pass while the
resource_cleanup fails on classlevel instead of the test fail.
Maintaine and support proper cleanup ordering when functions
are classbase while other instances.
Current fix contains class descriptor that learn caller
in case its a class it will use the class cleanup
in case its an instance it will use instance cleanup.
Expecting to see failures due to wrong cleanup in tests
result from the wrong impelementaions.
Added unittests for cleanup_order decorator
Updated test_groups cleanup , volume can not be deleted
before group, class level cleanup hides it because group
clean was instance level.
See scenario methods as reference (manager)
Change-Id: I27328bf6c176840c7762bd97f596481ffa6f5736
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Added a waiter that compares the current status
of the port to a target value and returns the port
when that is achieved.
Closes-Bug: 1845486
Change-Id: Ibc5434244f3758c60ddefa96d78476948a47ed13
|
| |\ \ \ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
tempest-centos9-stream-fips job has a long history of runs resulting to
TIMED_OUT [1]
Since the job defines some extra tasks for enabling FIPS, we hardly hit
the default timeout of 2 hours as shown in every failing build log.
If we really want this job, then we need to give it some extra space as
for the moment, apart from wasting CI resources into continuously failing
runs, we don't see any interest in it.
[1] https://zuul.openstack.org/builds?job_name=tempest-centos9-stream-fips
Change-Id: I5b04d69f74854725e0c11abe58e936fc6d18d183
|
| |\ \ \ \ \ |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The 'all-plugin' tox environment was deprecated by this patch [1].
Instead of the 'all-plugin' it is recommended to use the 'all' tox
environment.
This patch removes any reference to 'all-plugin' tox environment and
updates the documentation so that the installation steps work with
the 'all' tox venv.
[1] https://review.opendev.org/c/openstack/tempest/+/543974
Related-Bug: 1862240
Change-Id: I0a86d9cf33bff6576a6337967d6b663ab7d9f4a6
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Tempest 33.0.0 has been released [1].
This commit adds a new page for 33.0.0 release notes.
[1] https://review.opendev.org/c/openstack/releases/+/866857
Change-Id: Ied05cbc02509ff5a98a75bf18d2f08c30a5601ae
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
tox.ini started failing with Tox4 which had some
incompatible changes. One is passenv where we need
to pass each value in newline otherwise, it fails with
error:
failed with pass_env values cannot contain whitespace,
use comma to have multiple values in a single line,
invalid values found.....
Also adding tempest in allowlist_externals as it is required
by unit test also.
Fixing tox.ini for tox4 changes.
Change-Id: I55cd9855d8232c007b012c19755c837e97823aea
|
| |\ \ \ \ \ \
| | |_|_|_|/
| |/| | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Adding placement service in 'enforce_scope' config
so that we can switch the placement scope and new defaults
and test them.
Change-Id: Ie9a4c22dee892eae84f35af2b6b5ff2098225495
|
| |\ \ \ \ \ \ |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Tempest 33.0.0 release hash is prepared[1] so we can
revert back to use the master constraints by default.
[1] https://review.opendev.org/c/openstack/tempest/+/864372/
Change-Id: I1a3cea4cc543aabe61483a32f71b2b9db178cecf
|
| |\ \ \ \ \ \ \
| |/ / / / / / |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
We are going to release Tempest new tag 33.0.0 to declare
the end of support for stable/wallaby. stable/zed constraint
is latest stable constraints tested with current tempest hash
which is going to be used for 33.0.0 release.
Further information:
https://docs.openstack.org/tempest/latest/requirement_upper_constraint_for_tempest.html
Change-Id: Ia8536e783df945a273b8697b128a5115104d3c12
|
| |\ \ \ \ \ \ \
| |/ / / / / / |
|
| | | |_|/ / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This marks the end of support for stable/wallaby
which is EM now [1]. This remove the stable/wallaby
jobs and also adds relesenote to mark the end of
support of Wallaby.
Depends-On: https://review.opendev.org/c/openstack/releases/+/862393
[1] https://releases.openstack.org/
Change-Id: Ie3bbbc80e4b2e7bca8e8b70fce1d31166220c6d3
|
| |\ \ \ \ \ \
| |/ / / / /
|/| / / / /
| |/ / / / |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We have many services (Nova, Neutron, Glance etc) implemented the
new RBAC (project scope and project personas). For these services,
all tests should pass as projects personas (project reader) does
not impact existing testing/usage.
keystone has system scope adopted in their policy for now which
we need to make it work for project scope also and until then
we will see test failing.
This commit adds a new tempest full job which enable the scope
and new defaults of RBAC for applicable services.
Depends-On: https://review.opendev.org/c/openstack/neutron/+/865040
Change-Id: Ib8f2f0e25205edba332fb9bd2a73012016d45061
|
| |\ \ \ \ \ |
|
