tempest volume quota validation breaks cinder stable/ocata runs

Bug #1843762 reported by Eric Harney on 2019-09-12
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Undecided
Unassigned
tempest
Undecided
Eric Harney

Bug Description

https://review.opendev.org/#/c/603339/ added validation to cinder APIs, this breaks cinder stable/ocata as seen on

https://review.opendev.org/#/c/681477/1/ in legacy-tempest-dsvm-neutron-full

tempest.lib.exceptions.InvalidHTTPResponseBody: HTTP response body is invalid json or xml
Details: HTTP response body is invalid ('groups' is a required property
Failed validating 'required' in schema['properties']['quota_set']:

Fix proposed to branch: master
Review: https://review.opendev.org/681776

Changed in tempest:
assignee: nobody → Eric Harney (eharney)
status: New → In Progress
Ghanshyam Mann (ghanshyammann) wrote :

new field 'groups' seems added in API response without new microversion ? if so then it seems API interoperability issue. All fields added/removed/updated in API response should be with new microversion.
This seems Cinder bug for me which is caught by Tempest schema validation.

Ghanshyam Mann (ghanshyammann) wrote :

On Ocata support from Tempest master-

Yeah, Tempest master does not support Ocata branch as this is in EM state. as per Tempest stable branch policy, if EM branch fails due to master changes then that branch needs to use Tempest working tag instead of Tempest master.[1]

We need to install Tempest v20.0.0 in Ocata.

[1] https://docs.openstack.org/tempest/latest/stable_branch_support_policy.html

Changed in tempest:
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers