Commit Graph

12797 Commits

Author SHA1 Message Date
Zuul
6555d7c98d Merge "Add cyborg-tempest-plugin to required-projects and remove octavia" 2019-05-17 20:57:48 +00:00
Zuul
3bc3acafee Merge "Remove legacy-periodic-tempest-dsvm-neutron-full-ocata" 2019-05-17 08:31:22 +00:00
Masayuki Igawa
7f5dd855c6
Add cyborg-tempest-plugin to required-projects and remove octavia
This commit adds opendev.org/openstack/cyborg-tempest-plugin to
required-projects to pass the plugin-sanity-check job. It's a new
tempest plugin. It doesn't work properly on master yet. So, I put it on
the BLACKLIST.

And this commit also removes octavia because octavia tempest tests were
already migrated to octavia-tempest-plugin, and there is no tempest test
in the octavia repo. The removal patch[0] in octavia was already merged.

[0] https://review.opendev.org/#/c/659516/

Change-Id: Ied13dbf774472e1c36dca4ccca157104a81fbf9d
2019-05-17 08:24:15 +09:00
Zuul
0557acd998 Merge "Revert "Refactor random naming"" 2019-05-16 23:08:18 +00:00
Zuul
51814c592c Merge "Remove airship-tempest-plugin from blacklist" 2019-05-16 20:53:29 +00:00
Zuul
2c36090a4b Merge "Make dns_servers option deprecated" 2019-05-16 20:52:17 +00:00
Masayuki Igawa
8460cb1844
Remove airship-tempest-plugin from blacklist
This commit removes airship-tempest-plugin entry from the BLACKLIST
since the patch was already merged. And airship/tempest-plugin has a
gate job to verify it, too. There is no reason to store it in the
BLACKLIST anymore.

And this commit also make plugin-sanity-check's basepython python3
because we should use it as a default.

Change-Id: I9c50d327df65fecf8510f6f54f06e9f42da9bea0
2019-05-16 18:48:27 +09:00
zhufl
e027ea931c Make dns_servers option deprecated
CONF.network.dns_servers is not used anywhere, so this is to deprecate it.

Change-Id: I60ecad0e58394dcf912164095922276f4340f90b
2019-05-16 13:46:23 +08:00
Andreas Jaeger
39fe695177 Remove legacy-periodic-tempest-dsvm-neutron-full-ocata
This job does not run - and our logs shows no invocation at all,
see
http://zuul.openstack.org/builds?job_name=legacy-periodic-tempest-dsvm-neutron-full-ocata

Remove it.

Change-Id: Ib71d0a1d4e4650f07c8162f848def09724f1e987
2019-05-15 19:39:42 +02:00
Zuul
ab3f72b214 Merge "Make test_hotplug_nic test first check the IP" 2019-05-14 09:25:43 +00:00
Martin Kopec
925188d2d5 Make test_hotplug_nic test first check the IP
The test doesn't take into account that the interface can
already be associated with the IP address, configured by
NetworkManager. Therefore the review adds a check if the
IP is already set.

Change-Id: I4eede97c041b44d9a7bb754e5ccc1ebb194a2e4b
2019-05-10 07:11:36 +00:00
Zuul
6f07d49044 Merge "Use show_quota_class_set after update_quota_class_set" 2019-05-09 05:45:46 +00:00
Zuul
7fb6e81027 Merge "Introduce an attached volume migration test" 2019-05-07 09:19:13 +00:00
Zuul
2e11ca3856 Merge "Add assertions to attached volume retype test" 2019-05-07 09:04:12 +00:00
Zuul
7102321f82 Merge "[Trivial]Remove unused variable assignments" 2019-05-06 20:36:32 +00:00
Matt Riedemann
514495b1a0 Revert "Refactor random naming"
This reverts commit e3e7b2722e.

After that change, if the test creates a volume type with a
given name, it's not unique and therefore can hit a 409 conflict
trying to create a volume type with a name that already exists,
which can happen when running scenario tests concurrently since
several encrypted volume tests use the same volume type name "luks".

See Iecf62d411d2da17c4c983915018e3ed9180ecd11 for an
alternative but this is easier. It's not entirely clear
why the original change was made anyway - why do we care
if the tests create long names? They weren't unnecessary
because they were random to avoid conflicts.

Change-Id: I9f5a967514f3c79f861d286f65402e9ec2832cc4
Closes-Bug: #1826953
2019-05-04 13:39:24 -04:00
Doug Schveninger
23325c0ee8 Fix resource leaks in EndPointGroupsTest
Test cases were creating services at the test case
scope and not add them to addCleanup method.

Change-Id: I390f9e013930477f32c537191adbef37e1b4dd1c
2019-05-03 06:51:24 -05:00
Zuul
661a52ed45 Merge "Fix the bug of deleting security group after testing changing password." 2019-04-30 00:58:48 +00:00
zhufl
f5cff8b448 [Trivial]Remove unused variable assignments
This is to remove unused variable assignments in waiters.py.

Change-Id: Ib3a7943eabaf037540520d5e0e53750c4db5743d
2019-04-28 15:26:32 +08:00
zhangyangyang
c248f5962e Fix the bug of deleting security group after testing changing password.
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
2019-04-28 03:07:40 +00:00
Zuul
fc91681dda Merge "Uncap jsonschema" 2019-04-25 11:54:01 +00:00
Lee Yarwood
e5597401ff Introduce an attached volume migration test
This change introduces a true cinder host to host attached volume
migration test in addition to the existing attached volume retype test.
To enable this two new calls are introduced to the v3 volume client to
allow all volume backends to be listed per project and to also call for
a direct volume migration between backends.

Related-bug: #1803961
Depends-On: I1bdf3431bda2da98380e0dcaa9f952e6768ca3af
Change-Id: I501eb0cd5eb101b4dc553c2cdbc414693dd5b681
2019-04-25 10:34:58 +01:00
zhufl
2b1751e461 Use show_quota_class_set after update_quota_class_set
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
2019-04-24 11:05:11 +08:00
Lee Yarwood
8df5fdcbe0 Add assertions to attached volume retype test
Previously only the volume type and timestamp data was checked when
retyping an attached volume. This change adds additional assertions to
ensure the volume state remains `in-use`, volume migration state is
`success` and the same `volume_id` remains attached to the instance
after the retype completes. This final check ensures that nova has
correctly called the os-migrate_volume_completion cinder API.

Related-bug: #1803961
Change-Id: I32f0611bdfd2ccede73e7ab774286f5315ff92c3
2019-04-23 17:42:26 +01:00
OpenDev Sysadmins
682965e392 OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
2019-04-19 19:29:35 +00:00
Zuul
ded3516406 Merge "Fix invalid filter passed to list_volumes" 2019-04-18 17:32:48 +00:00
Zuul
c1454fc66b Merge "Fix test_volume_swap_with_multiattach" 2019-04-17 21:11:08 +00:00
Zuul
845780d4c0 Merge "Add the api type check when check the param of api_microversion" 2019-04-17 20:29:34 +00:00
chenke
4beff29c36 Add the api type check when check the param of api_microversion
When I specified COMPUTE_MICROVERSION = 2.53,
the error message made me confused. It doesn't
tell me whether the type I set is int or a string,
so I recommend adding a type check.

Change-Id: I620c90f1652fa22bff2ffff9b84b1addc31285ff
2019-04-17 10:00:02 +08:00
zhufl
9a740dd262 Fix invalid filter passed to list_volumes
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
2019-04-17 01:52:28 +00:00
Zuul
fab49c44f8 Merge "Ensure all image cache volumes are removed before removing the volume type" 2019-04-15 11:03:39 +00:00
Zuul
e6057592fb Merge "Add unstable_test decorator" 2019-04-12 05:48:13 +00:00
Slawek Kaplonski
21f53012f7 Add unstable_test decorator
This decorator can be used to temporarily mark some tests as unstable.
This may help sometimes to debug such test which is failing often
but not always in the gate because it will still be run but will
not cause all job failure when it fails.

This may be also used to easily track in logstash how often
such test is failing by looking for describption of unstability
reason set in decorator.

Change-Id: I79ce70f479506ec2b3216747d533ff2e450685aa
Related-Bug: #1813198
2019-04-11 17:42:40 +00:00
Zuul
69761f5a44 Merge "Skip test_volume_backup_create_get_detailed_list_restore_delete" 2019-04-11 08:16:10 +00:00
Ghanshyam Mann
762e98c237 Skip test_volume_backup_create_get_detailed_list_restore_delete
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
2019-04-11 07:20:14 +09:00
Trevor McCasland
7ea7e0a14e update identity role tests to work w/ pre-prov
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
2019-04-09 16:46:52 +00:00
Lee Yarwood
be64e1ae7c Ensure all image cache volumes are removed before removing the volume type
Previously the only clean up action registered when creating a new
volume type was the direct removal of that type. However this request would
silently fail in the attached volume migration scenario tests if the
backends being used had their image volume cache enabled.

This was due to the image volume cache still containing volumes
associated to the given volume type when attempts were made to delete
the volume type. To avoid this these image volume cache volumes must be
manually removed by an admin user before deleting the volume type.

Closes-Bug: #1823880
Change-Id: Ib4d82586e91037729f9e846a6f0fac6d393ca475
2019-04-09 17:22:51 +01:00
Zuul
3c5b61396d Merge "Run integration jobs for requirements.txt changes" 2019-04-09 05:53:41 +00:00
Zuul
e1bc201c57 Merge "Improve router deletion logging in tempest cleanup" 2019-04-08 22:05:42 +00:00
Zuul
13bbcdd6bf Merge "Improve logging in tempest cleanup" 2019-04-07 02:52:37 +00:00
ghanshyam
77a1933bd3 Run integration jobs for requirements.txt changes
currently we do not run the gate jobs if any change is for
test|requirements.txt only which can break the things.
Example- https://review.openstack.org/#/c/649804/

Because Tempest does not have functional testing which might
be enough for teting the requirement change, we start running
the all gate jobs for such change.

Change-Id: I54384f5c664673ef32937cd1d7c4a46c10c18f9b
2019-04-06 17:55:21 +00:00
Tony Breeds
a7f16b291d Uncap jsonschema
We have jsonschema capped at a fairly old version. Other than some
specific releases, it looks like keeping it below 3.0 was added in
I943fd68b9fab3bce1764305a5058df5339470757 without really any explanation
why.

In order to update to a 3.x release we need to:
1. Remove the cap from global-requirements.txt (see Depends-On), leaving
   upper-constraints.txt at a 2.x release
2. Remove the cap from all consumers (this change)
3. Release a new version of consumers that are published to pypi
4. Update upper-constraints.txt with those new releases
5. Update jsonschema in upper-constraints.txt to a 3.X release
   (See: https://review.openstack.org/649789)
6. Test consumers with the change from 5.
7. [Optional] fix issues in consumers that arise from 6.
8. Merge the change from 5.

Change-Id: I95b5520ca0e8da7b2a7663a272bc740b8c809592
Co-Authored-by: Sean McGinnis <sean.mcginnis@gmail.com>
Depends-On: https://review.openstack.org/649669
2019-04-04 14:01:16 +11:00
Matt Riedemann
1bbfa121b3 Fix test_volume_swap_with_multiattach
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
2019-04-03 08:17:04 +00:00
Martin Kopec
598b1ae854 Improve router deletion logging in tempest cleanup
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
2019-04-02 12:51:44 +00:00
Zuul
3639f91c36 Merge "Add missing validation for the compute/positive" 2019-04-02 09:55:36 +00:00
Zuul
b3a16b5d4f Merge "Init placement client in tempest Manager object" 2019-04-02 01:32:31 +00:00
Zuul
a415f6b1cc Merge "Add Tempest gate job for stable/stein" 2019-04-02 00:30:25 +00:00
Zuul
49e9de05ec Merge "Mention autopep8 in Hacking.rst" 2019-04-01 14:50:50 +00:00
Martin Kopec
fd01fe9445 Improve logging in tempest cleanup
Add id or name of the resource which failed to delete
to the logging.

Change-Id: I04b04406e3917a63332199adf5c15b8e4ed6ca5a
2019-04-01 14:31:43 +00:00
Archit Modi
a8cb701cc0 Init placement client in tempest Manager object
Placement client is not yet added/initialized in
the tempest/clients.py Manager object.

Change-Id: I19224b178e2860ee29c56546340cee36cd71b0e8
2019-04-01 09:35:42 -04:00