[qa][stable] tempest.api.volume.test_versions.VersionsTest.test_show_version fails on stable/pike
A new test was recently added to tempest [1] which uses the volume API v3 client to list and show versions and compare those against the response schema. It's failing against stable/pike changes [2] presumably because the volume v3 API does not show the (deprecated) v1 API, though I'm a bit confused because the test is doing a GET / and then for each version in the response it's doing a GET /{version}/ so I'm not sure what's up with cinder's pike API version interface where it would list a version but not be able to show it.
Anyway, it sounds like this is another case where we're going to have to pin tempest to a tag in devstack on stable/pike to continue running tempest jobs against stable/pike changes, similar to what recently happened with stable/ocata [3].
[1] https://review.opendev.org/#/c/680790/ [2] https://145b0d5be77f0cbe05ff-d67a6226f6eb6d34ab4efd951744a16f.ssl.cf5.rackcd... [3] https://review.opendev.org/#/c/681950/
On 9/25/2019 9:51 AM, Matt Riedemann wrote:
Anyway, it sounds like this is another case where we're going to have to pin tempest to a tag in devstack on stable/pike to continue running tempest jobs against stable/pike changes, similar to what recently happened with stable/ocata [3].
Here is the devstack patch to pin tempest to 21.0.0 in stable/pike:
https://review.opendev.org/#/c/684769/
On Wed, Sep 25, 2019 at 10:00:30AM -0500, Matt Riedemann wrote:
On 9/25/2019 9:51 AM, Matt Riedemann wrote:
Anyway, it sounds like this is another case where we're going to have to pin tempest to a tag in devstack on stable/pike to continue running tempest jobs against stable/pike changes, similar to what recently happened with stable/ocata [3].
Here is the devstack patch to pin tempest to 21.0.0 in stable/pike:
https://review.opendev.org/#/c/684769/
--
Thanks,
Matt
We should be seeing this in queens too. We will need to get this patch merged there first, then into pike. We can either pin tempest, or get this fixed.
https://review.opendev.org/#/c/684954/
It was a long standing issue that disabled API versions were still listed. This can probably be backported back to ocata.
Sean
---- On Thu, 26 Sep 2019 02:09:20 -0500 Sean McGinnis sean.mcginnis@gmx.com wrote ----
On Wed, Sep 25, 2019 at 10:00:30AM -0500, Matt Riedemann wrote:
On 9/25/2019 9:51 AM, Matt Riedemann wrote:
Anyway, it sounds like this is another case where we're going to have to pin tempest to a tag in devstack on stable/pike to continue running tempest jobs against stable/pike changes, similar to what recently happened with stable/ocata [3].
Here is the devstack patch to pin tempest to 21.0.0 in stable/pike:
https://review.opendev.org/#/c/684769/
--
Thanks,
Matt
We should be seeing this in queens too. We will need to get this patch merged there first, then into pike. We can either pin tempest, or get this fixed.
https://review.opendev.org/#/c/684954/
It was a long standing issue that disabled API versions were still listed. This can probably be backported back to ocata.
I do not think the cinder backport will fix the issue. In my test patch, its v1 version which causing the issue and v1 should not be returned in GET / as per cinder pike code. 684954 is only taking care for v2 and v3 things if those are disabled.
- https://zuul.opendev.org/t/openstack/build/e13e8a408f214e1b9d03b41c23955c7e/...
Something else is causing this issue.
-gmann
Sean
---- On Wed, 25 Sep 2019 09:51:15 -0500 Matt Riedemann mriedemos@gmail.com wrote ----
A new test was recently added to tempest [1] which uses the volume API v3 client to list and show versions and compare those against the response schema. It's failing against stable/pike changes [2] presumably because the volume v3 API does not show the (deprecated) v1 API, though I'm a bit confused because the test is doing a GET / and then for each version in the response it's doing a GET /{version}/ so I'm not sure what's up with cinder's pike API version interface where it would list a version but not be able to show it.
Yeah, it is not so clear from failure and logs that which version is missing. let me add more clear logs in tests.
Seems like cinder v1 version got removed from the list as well as from show API at the same time - I03bf2db5bd7e2fdfb4f6032758ccaf2b348a82ba
-gmann
Anyway, it sounds like this is another case where we're going to have to pin tempest to a tag in devstack on stable/pike to continue running tempest jobs against stable/pike changes, similar to what recently happened with stable/ocata [3].
[1] https://review.opendev.org/#/c/680790/ [2] https://145b0d5be77f0cbe05ff-d67a6226f6eb6d34ab4efd951744a16f.ssl.cf5.rackcd... [3] https://review.opendev.org/#/c/681950/
--
Thanks,
Matt
---- On Wed, 25 Sep 2019 13:20:23 -0500 Ghanshyam Mann gmann@ghanshyammann.com wrote ----
---- On Wed, 25 Sep 2019 09:51:15 -0500 Matt Riedemann mriedemos@gmail.com wrote ----
A new test was recently added to tempest [1] which uses the volume API v3 client to list and show versions and compare those against the response schema. It's failing against stable/pike changes [2] presumably because the volume v3 API does not show the (deprecated) v1 API, though I'm a bit confused because the test is doing a GET / and then for each version in the response it's doing a GET /{version}/ so I'm not sure what's up with cinder's pike API version interface where it would list a version but not be able to show it.
Yeah, it is not so clear from failure and logs that which version is missing. let me add more clear logs in tests.
Seems like cinder v1 version got removed from the list as well as from show API at the same time
- I03bf2db5bd7e2fdfb4f6032758ccaf2b348a82ba
Logs were missing for show_version because it directly call raw_request() which does not do logging. Adding the logging for rest_client raw_request() also so that we can check the failed version info - https://review.opendev.org/#/c/684858/
testing here - -https://review.opendev.org/#/c/684859/
-gmann
-gmann
Anyway, it sounds like this is another case where we're going to have to pin tempest to a tag in devstack on stable/pike to continue running tempest jobs against stable/pike changes, similar to what recently happened with stable/ocata [3].
[1] https://review.opendev.org/#/c/680790/ [2] https://145b0d5be77f0cbe05ff-d67a6226f6eb6d34ab4efd951744a16f.ssl.cf5.rackcd... [3] https://review.opendev.org/#/c/681950/
--
Thanks,
Matt
participants (3)
-
Ghanshyam Mann
-
Matt Riedemann
-
Sean McGinnis