summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Create releasenotes page for tempest 34.2.0HEADmasterGhanshyam Mann2023-05-092-0/+7
| | | | Change-Id: Ibc48eedb6c1fe7defca878c10805484b07b3f624
* Also require resources for PINGABLEDan Smith2023-05-051-5/+4
| | | | | | | | This adds to the existing check to make sure that if a test requires PINGABLE state that they provide the validation resources and flags necessary to do that validation. Change-Id: I0620fd93ee2dc37e53ae991967321f88cf9d67a8
* Make volumes_backup test wait for SSHABLEDan Smith2023-05-051-1/+7
| | | | Change-Id: If3514e140739d8663bfd28f40a649019e2544636
* Switch to the master constraint in tox.iniGhanshyam Mann2023-05-051-5/+5
| | | | | | | | | | | To releas a new tag for Tempest, we modified the compatible constraint in tox.ini - https://review.opendev.org/c/openstack/tempest/+/882354/ As new tag is released now so we can switch back to the master constraint in tox.ini. Change-Id: Ic4f60c6a1b8b657edf06cffc9165c49da4395389
* Use stable constraint in tox to release Tempest new tag34.2.0Ghanshyam Mann2023-05-051-5/+5
| | | | | | | | | | | | | We are going to release Tempest new tag which work with the stable/2023.1 constraint so use that 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: I81c251c7f006b8792c006db88bd47fdb40df14a1
* Add release notes for 2023.2 cycle intermediate release.Ghanshyam Mann2023-05-051-0/+5
| | | | Change-Id: I02c033604eb7e5bde5fb0e984d2d143abde2cbe8
* Allow passing validation_resources in scenarioDan Smith2023-05-041-4/+8
| | | | | | | | | | | | In the scenario manager, we need to pass through validation parameters if they are passed to us. If not, we need to do the needful for SSHABLE targets, but some tests need to pass in their own. Note that the scenario manager create_server() already has a validatable parameter, but it does *not* pass that through to create_test_server(), so we also need to fix that up for those cases to avoid tripping over the assertion requirement that it be provided. Change-Id: I44b3deba70e3f33f1287a6b3f28c21da5492cc04
* Fail create if validation flags do not agreeDan Smith2023-05-025-6/+16
| | | | | | | | | | | | | | | | | | This makes us sanity check the wait_until, validateable, and valiadation_resources flags we get in create_test_server(). Specifying wait_until='SSHABLE' without the other two will silently not actually wait for the server to be sshable. Help make this harder to do by making create_server in the volumes base class ensure we pass validation_resources for tests that request SSHABLE. Note this also includes a change to get_class_validation_resources() to make sure it returns an empty dict just like get_test_validation_resources() does if/when CONF has validation disabled. Change-Id: Ic8ae7bb322eaf1294d48d5f5242365bec5e863e2
* Allow wait_until=SSHABLE in scenario managerDan Smith2023-05-024-8/+58
| | | | | | | | | | | | | If we can, we should always wait for servers to be ssh'able before we try to do things to them, especially attach volumes. This improves stability of the tests, at the expense of performance. This also makes some volume-having scenario tests wait for SSHABLE. The ones that don't are already using ssh to do things like create and check timestamps, so they need not be changed to still have this behavior. Change-Id: I169d8d119758e4f5e79c42cfd458577a67b13fc5
* Actually make volume extend tests validateDan Smith2023-05-012-1/+6
| | | | | | | | | This fixes the previous patch to *actually* wait for the server to be SSHABLE before continuing the test. Because the volumes tests don't have full networking and we didn't provide validation resources to create_server() we weren't *actually* doing the wait for ssh. Change-Id: I783bbed4bea6137de3afa9a7ecd1a9cd37bb17e8
* Merge "Wait until SSHABLE in volumes_extend test"Zuul2023-04-301-1/+1
|\
| * Wait until SSHABLE in volumes_extend testDan Smith2023-04-281-1/+1
| | | | | | | | Change-Id: Id6f4f7dd842cf7f578c37a64ee5c9f46c0a893f2
* | Merge "Update v3_endpoint_type to use public"Zuul2023-04-302-4/+8
|\ \
| * | Update v3_endpoint_type to use publicArx Cruz2023-04-282-4/+8
| |/ | | | | | | | | | | | | The default endpoint type for OpenStack Identity should be the public version, and it was something missed for a while. Change-Id: Ib679fb21d8d815317ecdd03e40dfe16e6ef3915e
* | Merge "Update "test_list_migrations_in_flavor_resize_situation" to indicate ↵Zuul2023-04-281-3/+5
|\ \ | |/ |/| | | the failing request on timeout."
| * UpdateJorge San Emeterio2023-03-141-3/+5
| | | | | | | | | | | | | | | | | | "test_list_migrations_in_flavor_resize_situation" to indicate the failing request on timeout. This is one of those tests that for some reason or the other fail randomly on our CI systems. Problem is, that the error message it fails with is not very helpful, as it just indicates that a timeout happened but not much else. This change seeks to fix that by including the request id that led to the timeout. This way, once the test fails on a build, it will be possible to search the log files for this request and track the underlying problem. Closes-Bug: #2009701 Change-Id: Ic1ffd62f9d6ed0d69467f678c1820cddbb1fda12
* | Simplify definition of fips jobsAde Lee2023-04-172-6/+2
| | | | | | | | | | | | | | | | | | | | With the new base jobs, it is no longer necessary to define a pre-run playbook. You simply need to set enable_fips to True and specify an nslookup_target. This will set things up to use ubuntu jobs when FIPS is supported on jammy Depends-On: https://review.opendev.org/c/openstack/devstack/+/871606 Change-Id: I1c02c4817a39d26e94873831801089d1aa86133c
* | Merge "Add project reader to account-generator"Zuul2023-04-042-21/+30
|\ \
| * | Add project reader to account-generatorLukas Piwowarski2023-03-302-21/+30
| |/ | | | | | | | | | | | | | | | | | | | | | | Tempest requires project_reader to sucessfully run some tests [1]. However, account-generator does not support generating project reader accounts. This patch therefore changes accout-generator so that it generates project reader together with other accounts. [1] https://review.opendev.org/c/openstack/tempest/+/871210 Change-Id: Ie127c2ed159da8a6bc780919cdd4def44e457efb
* | Merge "Add RBAC new defaults and scope job for stable/zed"Zuul2023-03-232-0/+8
|\ \
| * | Add RBAC new defaults and scope job for stable/zedGhanshyam Mann2023-03-222-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | stable/zed has the new defaults and scope available but they were disabled by default. Let's test those by enabling in stable/zed also so that we know if they work fine in integrated way or not Change-Id: Id2bd58854f60f38dccf0ef805de284c7e95db2f3
* | | Merge "rm hardcoded cidr in test_create_server_multi_nic"Zuul2023-03-231-13/+35
|\ \ \ | |/ / |/| |
| * | rm hardcoded cidr in test_create_server_multi_nicPragadeeswaran Sathyanarayanan2023-03-211-13/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Now, We have some hard code in here, but some VPC are limited to some specific address ranges by default in some cloud. So, we need change these hard code to configuration, it can meet the user specific requirement flexibly and reasonably. closes-bug: #1743742 Signed-off-by: Pragadeeswaran Sathyanarayanan <psathyan@redhat.com> Change-Id: Ia201c0520b8d2df17664b84bd61755d7c2d68258
* | | Update integrated gates template for grenade skip level jobGhanshyam Mann2023-03-201-0/+20
|/ / | | | | | | | | | | | | | | | | | | | | | | Current master is a non SLURP release so we do not need to run greande-skip-level job as default though any project want to run skip level testing they can use the greande-skip-level-always job for example nova doing. With branch variant, we make run no change in integrated gate jobs for stable/2023.1 testing. Change-Id: I183fe7513064d46255e8b078528d7e3639a3ce1a
* | Merge "Create releasenotes page for tempest 34.0.0"Zuul2023-03-192-0/+7
|\ \
| * | Create releasenotes page for tempest 34.0.0Ghanshyam Mann2023-03-172-0/+7
| | | | | | | | | | | | Change-Id: Ifceec758bd48c916682edb1db78585c87f7eb730
* | | Merge "Add Tempest gate job for stable/2023.1"Zuul2023-03-172-1/+27
|\ \ \ | |/ / |/| |
| * | Add Tempest gate job for stable/2023.1Ghanshyam Mann2023-03-152-1/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Now we have stable/2023.1 branch ready for devstack and so does for all service projects. This commit adds the Tempest testing for stable/2023.1 by adding new jobs running on stable/2023.1 version of openstack. Change-Id: I5994c6fb56e01c9697d4d80bcbff2939ef2eff04
* | | Merge "Inherit tempest-extra-tests job from tempest-full-py3"Zuul2023-03-171-1/+1
|\ \ \ | |/ /
| * | Inherit tempest-extra-tests job from tempest-full-py3Ghanshyam Mann2023-03-151-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | tempest-extra-tests job run the admin and negative tests for now which need same config what tempest-full-py3 job already have. Inheriting tempest-extra-tests job from tempest-full-py3 for the same reason. Change-Id: Idad488abb9cb6bd982f0193e7a2cc411156dd034
* | | Merge "Switch to the master constraint in tox.ini"Zuul2023-03-171-5/+5
|\ \ \
| * | | Switch to the master constraint in tox.iniGhanshyam Mann2023-03-161-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | To releas a new tag for Tempest 2023.1, we modified the compatible constraint in tox.ini - https://review.opendev.org/c/openstack/tempest/+/877713 As new tag is released now so we can switch back to the master constraint in tox.ini. Change-Id: Ic91e443ae1948d71fa276be03dcef4576c64df33
* | | | Merge "Use stable constraint in tox to release new tag for 2023.1"34.1.0Zuul2023-03-171-5/+5
|\ \ \ \ | |/ / /
| * | | Use stable constraint in tox to release new tag for 2023.1Ghanshyam Mann2023-03-161-5/+5
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We will release Tempest new tag to get cinder tests fix[1] in stable/2023.1. Without the cinder test fix[1], tempest released for 2023.1 will not work with cinder in 2023.1. So that new tag use stable/2023.1 constraint in the tox env. For example: if anyone uses 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. [1] https://review.opendev.org/c/openstack/tempest/+/875372 Change-Id: Ibb348e0642190b3a83d8b5f86c8b49295cf071e0
* | | Merge "Update multiattach tests"Zuul2023-03-174-5/+14
|\ \ \ | |/ /
| * | Update multiattach testswhoami-rajat2023-03-154-5/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Multiattach tests use legacy format to create multiattach volumes i.e. provide "multiattach=True" in request body of a create volume operation. This patch updates the multiattach tests to use multiattach volume type, which is the standard and only way[1], to create multiattach volumes. Note that the old functionality will be changed by patch[2] and passing multiattach=True in volume create request body will error out with BadRequest. Devstack will create the multiattach volume type, like an operator will create in a real deployment, and set it as a tempest config option (see depends on patch). We are adding a new config option `volume_type_multiattach` which is used as the multiattach volume type to create multiattach volumes. [1] https://docs.openstack.org/cinder/latest/admin/volume-multiattach.html#how-to-create-a-multiattach-volume [2] https://review.opendev.org/c/openstack/cinder/+/874865 Depends-On: https://review.opendev.org/c/openstack/devstack/+/877337 Depends-On: https://review.opendev.org/c/openstack/devstack/+/877497 Depends-On: https://review.opendev.org/c/openstack/devstack/+/877548 Depends-On: https://review.opendev.org/c/openstack/devstack/+/877498 Depends-On: https://review.opendev.org/c/openstack/devstack/+/877499 Change-Id: I5f68ef56fcc55dfc636936dabb5e6ad761579519
* | | Merge "Introduce a change that will allow more clients to make volumes"Zuul2023-03-131-14/+28
|\ \ \ | |_|/ |/| |
| * | Introduce a change that will allow more clients to make volumesMilana Levy2023-03-131-14/+28
| | | | | | | | | | | | | | | | | | | | | This change was written so that a new volume could be created by another client other than the primary admin. This change also let this clients to attach/detach volumes. Change-Id: I122a08aaf273a1f786e13737f31f2a0ab9c7bfdb
* | | Merge "Revert "Fix DeprecationWarning of jsonschema""Zuul2023-03-061-2/+2
|\ \ \
| * | | Revert "Fix DeprecationWarning of jsonschema"Ghanshyam2023-03-031-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit d52fb8cb6d2ed8893bc36f2f1f786cd890b1732e. Reason for revert: We need to support till xena as Tempest master do support stable/xena onwards branches. stable/xena has jsonschema 3.2.0 only https://github.com/openstack/requirements/blob/stable/xena/upper-constraints.txt#L548 We need to avoid such bumping unless something is failing. With jsonschema 3.2.0 we do not have the new things so let's keep them and we can fix it once we have jsonschema version as upper-constraint where they are going to be removed. https://github.com/python-jsonschema/jsonschema/blob/v3.2.0/jsonschema/validators.py#L475 Change-Id: Iab8dbcd469e2ca234c9a42673b8b02f470ec2404
* | | | Merge "Fix server cleanup in test_multiple_create test"Zuul2023-03-051-0/+8
|\ \ \ \
| * | | | Fix server cleanup in test_multiple_create testLukas Piwowarski2023-03-031-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The above-mentioned test uses ServersClient.delete_server function to delete servers. However, this function does not wait for the successful deletion of the servers which sometimes leads to an error (see linked bug). This patch changes the test so that it uses BaseV2ComputeTest.delete_server function which waits for the successful deletion of the server. Closes-Bug: #1954535 Change-Id: Ic1ed48fda03ce3c13198d2dd299b57d68b06e63d
* | | | | Merge "Revert "Update required minimum jsonschema version >= 4.16.0""Zuul2023-03-051-1/+1
|\ \ \ \ \
| * | | | | Revert "Update required minimum jsonschema version >= 4.16.0"Ghanshyam2023-03-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit e2315c1cf55b8eb7996c61bed85313d5ff90d07f. Reason for revert: We need to support till xena as Tempest master do support stable/xena onwards branches. stable/xena has jsonschema 3.2.0 only https://github.com/openstack/requirements/blob/stable/xena/upper-constraints.txt#L548 We need to avoid such bumping unless something is failing. Change-Id: Ib6c9ed442b9e4b6c70af7ca7e495e644b17428d7
* | | | | | Merge "Cinder client fails if identity API version specified"Zuul2023-03-021-2/+7
|\ \ \ \ \ \
| * | | | | | Cinder client fails if identity API version specifiedTakemi Asakura2023-03-011-2/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The `CLIClient` class, which is used as an interface to various openstack related CLIs, however, the `--os-identity-api-version` option is not available outside of swift and openstack client. When `--os-identity-api-version` is used except for swift and openstack clients, the following fixes were made to prevent passing options to the client. - Add a statement in the `cmd_with_auth` method that `--os-identity-api-version` is used only for swift and openstack Closes-Bug: #1980252 Change-Id: I8cfe63551cadd2f773c7455786b01f12e4843796
* | | | | | | Merge "Update required minimum jsonschema version >= 4.16.0"Zuul2023-03-021-1/+1
|\ \ \ \ \ \ \ | | |/ / / / / | |/| | | | |
| * | | | | | Update required minimum jsonschema version >= 4.16.0Nozomi Kawamoto2023-03-011-1/+1
| | |_|/ / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | DeprecationWarnings for jsonschema has been fixed at below path. https://review.opendev.org/c/openstack/tempest/+/875264 But it is required to update the minimum jsonschema version >= 4.16.0 for including a below commit. https://github.com/python-jsonschema/jsonschema/commit/ee024ffc61bee56b25e816f489d7365fe1445c6d Closes-Bug: #2008490 Change-Id: I0f459d7f74406e30af725c751f3b7cd1a6a931a6
* | | | | | Merge "Avoid wait for vol detach in live-migrate tests"Zuul2023-03-012-3/+5
|\ \ \ \ \ \
| * | | | | | Avoid wait for vol detach in live-migrate testsDan Smith2023-02-272-3/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This extends the recent theme of making sure the tearDown process does not hang and ultimately fail the test because it cannot detach a volume from a guest. We see (and have been seeing for a long time) the live migration tests specifically fail in this way in the gate. Change-Id: Ib1065c146ab2f927c23fc8a0b73d7040516a19a6 Related-Bug: #199232
View Lorry Controller Status