Thorough replacement of git.openstack.org and review.openstack.org URLs
with their opendev.org counterparts.
Change-Id: I88e894db7b854d32593c770f5aa9b8a91fad7866
When executed by python3 the test failed on a mismatch_error
caused by the fact that map function works differently in
python3.
The review fixes the issue by rewriting the line filtering
extensions to list comprehension.
Closes-Bug: #1829475
Change-Id: Ic2db882e505e7992192767acbe12a153b2d879e9
When deleting security group before vm is deleted, we will get 'the
security group is in use' error, so this is to add addCleanup to ensure
the vm is deleted before deleting security group.
Closes-Bug:#1826301
Change-Id: I3d4a3816196f42af3ea3f891473d09208651ae68
In cleanUp methods there is no need to fail test if Neutron returns
404 for DELETE request.
This commit adds test_utils.call_and_ignore_notfound_exc helper function
to be used in cleanup of Neutron resources.
Change-Id: I2c394d3219e16f653343d7043d36f55048f211dd
Closes-Bug: #1824018
In test_update_default_quotas, we should use show_quota_class_set
after update_quota_class_set to check whether the quota values
are really changed.
Besides, some LOG messages look odd and maybe being used as comments
are more suitable.
Change-Id: I05e22c88e184df7d425411051c2a8bf846cb35ee
display_name is not a valid filter for list_volumes, i.e., for non-admin
users no matter what value we set for display_name filter, all volumes
will be returned. We'd better to use name filter for it works all the
time.
https://github.com/openstack/cinder/blob/master/doc/source/admin/generalized_filters.rst
Change-Id: Ib25f4767b74d4494edfafa211d5884a01c1b6488
APIMicroversionFixture is used to set the microversion on
service clients which will take care of reseting the microversion.
This interface has been added to set the microversion on all supported
service clients which use microverison. User can set multiple
service microversion all together.
Using the new interface in compute tests to make sure it is all
working in serial and parallel testing.
Change-Id: I6ed41b02041d38c2c92c58b0d3dd6613d03da3f7
This test is very unstable and failing very frequently now a days
19 fails in 24 hrs / 137 fails in 10 days
- http://status.openstack.org/elastic-recheck/#1483434
Let's skip this until bug is fixed to avoid unstable gate.
Related-Bug: #1483434
Change-Id: Id107766126b31028920092ab098b084557d327cf
I don't see any limitations by using pre-provisioned
credentials for these tests:
* test_role_create_update_show_list
* test_list_roles
* test_implied_roles_create_check_show_delete
* test_roles_hierarchy
* test_assignments_for_implied_roles_create_delete
* test_domain_roles_create_delete
* test_implied_domain_roles
* test_assignments_for_domain_roles
* test_list_all_implied_roles
* test_grant_list_revoke_role_to_user_on_project
* test_grant_list_revoke_role_to_user_on_domain
* test_grant_list_revoke_role_to_group_on_project
* test_grant_list_revoke_role_to_group_on_domain
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: Id82f3b6187e878abe04a0aea9e7dbb9e8fb6360e
Nova change https://review.openstack.org/572790/ is fixing
a bug such that the compute API would allow people to
swap from a multiattach volume with multiple read/write
attachments, which could lead to data loss if the
secondary attachment is writing to the source volume while
it's being copied to the target volume.
As a result, test_volume_swap_with_multiattach needs to be
changed such that the volume we're swapping from has only
read-only attachments.
Change-Id: Ida387c600016b451e01118bc2c76662b46670288
Related-Bug: #1775418
Similarly to the interfaces, the volume detach can
fail if the vm is not ready for processing the acpi
signals. The ssh daemon allow to login around the same
time so it will helps to avoid detach failures.
Change-Id: Ic43ae3b76467a5cbeb6c2fe128435d64ab7743b5
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
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
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
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
No need for dynamic credentials to test showing the default domain.
By setting this value to False, consumers with an immutable user source
can execute this test.
Depends-On: I83a9b8af775580d36a1141be55e9c1cc283a75b6
Partial-Bug: #1714277
Change-Id: Ib85691ae3f7b5a4d4a9da620b6ec46c44380ef03
Some systems require strong passwords, so we'd better
use data_utils.rand_password() to create password when
creating user, to avoid password strength validation error.
Change-Id: I503ba6e068b6f7c8487b7077637ee21a9c104595
I don't see any limitations by using pre-provisioned
credentials for these tests:
* test_group_create_update_get
* test_group_users_add_list_delete
* test_list_user_groups
* test_list_groups
Change-Id: Id22911035ce880ab1faa9b37b238b9372ae98087
Based on average test times from the last 300 runs
of the tempest-full job [1] this change marks the
test_attach_detach_volume test as slow but only if
SSH validation is enabled, which it is in tempest-full
but might not be in other jobs that run it, for example
in refstack which uses this test for interoperability
certification.
[1] http://paste.openstack.org/show/745114/
Change-Id: I47710321d8dfb0345c793e66bd09a5dd1933557b
Related-Bug: #1783405
I don't see any limitations by using pre-provisioned
credentials for these tests:
* test_project_create_with_domain
* test_project_create_with_parent
* test_create_is_domain_project
* test_project_get_equals_list
* test_project_create_with_description
* test_associate_user_to_project
* test_project_create_enabled
* test_project_create_not_enabled
* test_project_update_name
* test_project_update_desc
* test_project_update_enable
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.
Change-Id: Ifc9f23d150992cdcf415293439c2f51f3d75aeb3
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.
Partial-Bug: #1777047
Change-Id: I8a0d5935b695a1649b204bd3c3351f34a80e9059
I don't see any limitations by using pre-provisioned
credentials for this test:
* test_list_regions_filter_by_parent_region_id
* test_create_region_with_specific_id
* test_create_update_get_delete_region
* test_list_regions
By setting force_tenant_isolation=False this test can now
be executed with backends that don't allow user creation
(immutable user source) like LDAP.
Change-Id: Ifad293dddb7c7fe76005761b43e1252e40ce7bdc
Zuul