Improve logging in tempest cleanup when a router and
its interfaces are being deleted. The review adds a
try except block for every attempt to remove a port.
By that addition any port error will not be hidden
behind the router error the port is attached to.
It will provide more precise error logging.
Change-Id: I475deec7b29600627f68ff07c5546e55cdab100f
Tempest 20.0.0 has been released [1].
This commit adds a new page for 20.0.0 release notes.
[1] https://review.openstack.org/#/c/645867/
Change-Id: Ic946b84e0003cc4cca85c1922816b8a0a3b8a3bf
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: Iff8f93426925a3480cedfb899216e443b12cd826
This commit adds the releasenote to tag Tempest for Stein
and needed for version 20.0.0 to release.
This relesenote also mark end of support for Ocata release as
ocata is in EM state.
Once we release the Tempest 20.0.0, we will remove the ocata job
from master gate.
Change-Id: I93bf37e31497881536b85783dc3cff70a56b04cb
Seems this variable is setup from gabbi-tempest, but other jobs also use
devstack-tempest.
Change-Id: I45c582d9d9b34a1c5ab75455e42077902cbb850e
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This PS will check config file passed from command line is actually
existing or not in tempest run command. If file exists, only then it
will go for set config path otherwise will fail with value error.
Also adding and modifying unit test cases for this change.
Partially-Implements: blueprint tempest-cli-unit-test-coverage
Change-Id: I09d756be69cb3a9be8d0638c41d45a089d62b238
Closes-Bug: #1808473
In test_add_remove_fixed_ip there is a potential issue where the user
running the test does not have the ability to create a server with a
fixed ip. As pointed out by zhufl (in review of change
I10a34fb12b595400fc15d935070f130c8e3d3963) This commit fixes the issue
so that we properly skip if tempest is not configured in a way where it
can create a server with the fixed ip.
Change-Id: Idcd66ac87cf156bc5c2b38178262c4686238bcd4
I don't see any limitations by using pre-provisioned credentials
for the tests:
* test_inherit_assign_list_check_revoke_roles_on_domains_group
* test_inherit_assign_check_revoke_roles_on_projects_group
* test_inherit_assign_list_check_revoke_roles_on_domains_user
* test_inherit_assign_list_check_revoke_roles_on_domains_group
* test_inherit_assign_check_revoke_roles_on_projects_user
* test_inherit_assign_list_revoke_user_roles_on_domain
* test_inherit_assign_list_revoke_user_roles_on_project_tree
By setting force_tenant_isolation=False these tests now be
can executed with backends that don't allow user creation
(immutable user source) like LDAP.
Partial-Bug: #1714277
Change-Id: I6b7bfbaef3355afede2adba56f342d5bfcbe3975
Nova has migrated the legacy-tempest-dsvm-nova-v20-api
job to zuulv3 native - "nova-tempest-v2-api"
This commit use the new job in tempest gate.
Change-Id: I81a07d8fbb529b0ac55ce40c50a6e5348e1f43df
If the keystone user source is immutable, such as an LDAP
active directory implementation, tempest tests that try
to create or delete a user will fail. Instead of failing,
we would like them to skip. This change uses a testtools
decorator to avoid unnecessary modifications and allow those tests
to skip.
Change-Id: Iba39c971468759d9b7b3f0382dfcb881cbb1801d
If the keystone user source is immutable, such as an LDAP
active directory implementation, tempest tests that try
to create or delete a user will fail. Instead of failing,
we would like them to skip. This change uses a testtools
decorator to avoid unnecessary modifications and allow those tests
to skip.
Parital-Bug: #1777047
Change-Id: I1d8105c24eb9b20e563de962f9e4d5776937126a
test_list_projects tests create a new domain and try to test the
list projects operation based on new domain-id. Keystone is
implementing the domain roles functionality for projects resource
- https://review.openstack.org/#/c/624218/
Which means listing the projects with authorized domain only.
This commit modify the tests to use the same domain as requester and
create project with that domain only not new one.
Also add the debug log.
Change-Id: I401815b4a0d3f7ad90801d5580897be870d33013
Before change Icb971831c8d4fe5f940d9e7993d53f1c3765e30f in devstack
in Rocky, the ENABLE_VOLUME_MULTIATTACH variable is used to control
whether or not the UCA is enabled on the node and defaults to False.
The tempest-slow job is multi-node and runs on stable branches since
change Ie5492603a12ca4ae56baa744bf650ae4d8036256 and as a result
is configuring the UCA on the subnode but not the controller, so
nova-compute on each node is running with different versions of QEMU
which can cause live migration failures if trying to live migrate
from a newer version of QEMU to an older version.
This fixes the issue by configuring the subnode with the correct
localrc value for ENABLE_VOLUME_MULTIATTACH.
Change-Id: Idea94dde6973805995c1678fcfb6b0e93025492a
Closes-Bug: #1819910
When importing unicode_literals from __future__ in tempest plugins as in
watcher, type is set as unicode instead of string when running in
python2, so the type is not properly detected. This is making that only
3 tests are detected as smoke in watcher tests plugins with python2 (other
may be affected) instead of 52 which are discovered as smoke with python3.
This patch uses six to make this compatible with both string and unicode
in python2.
Change-Id: Ibba9d8217f543fae0c232757ddb18c4fdf957aff
Co-Authored-By: yatin <ykarel@redhat.com>
the purpose of this change is to enable creating advance network
scenarios like checking connectivity from VM with port type "direct" to
VM with port type "normal".
with this change scenario planer can overwrite tempest.conf vnic_type
and port_profile paramters in scenario (ex. connectivty between VM
"direct" and VM "normal").
Change-Id: I5b9a4bd5350809d6b295dfede0c5059d01455404
autopep8 is an automated code formatting tool for python,
it does not know everything, also not super fast,
but it is faster than I can manually reformat the code.
tools/format.sh will call the formatting,
the tox will check did you called it.
Also adding a tox -eautopep8 way to use it.
autopep8 formats the lines in one way,
where tempest used a another way it was changed.
Change-Id: I6d51b14a5a5b87761071d0927fca23ba1651aa41
Below nodesets defined in Tempest are removed now:
- openstack-bionic-node This is unused after I5a24c697103090f6712d6e9168abe6c86f7c380c
- openstack-opensuse150-node is duplicate of devstack-single-node-opensuse-150
Depends-On: https://review.openstack.org/#/c/641746/
Change-Id: I39c03bfa52191a0b1acf6a73fa31b3c071ee60c1
This commit makes tempest-tox-plugin-sanity-check job
to run on Bionic. This job only run on master Tempest gate
so no need to worry about its xenial version.
Change-Id: I6d8c63a62416b35e9d203cbeabc9868aa6a95f44
oslo project provide jsonutils, and we use it in many place[1],
this PS to update the remained json moudule to oslo jsonutils for
consistency.
[1]: 9594233ffd/tempest/lib/services/volume/v1/quotas_client.py (L15)
Change-Id: Ib8d9f49a1fdfa0f5e0cfb05a193dffb83e4cfe69
