On 7/14/2016 4:40 PM, Matt Riedemann wrote:
On 7/14/2016 3:11 AM, GHANSHYAM MANN wrote:
1. Always add a schema change to Tempest if a microversion changes a
response.
The problem with this is we shouldn't land a schema change by itself
in tempest.
Until we have something using the schema we
On 7/13/2016 10:18 PM, Ken'ichi Ohmichi wrote:
Hi Matt,
2016-07-14 11:55 GMT+09:00 Matt Riedemann :
There are several changes in Tempest right now trying to add response schema
validation for the 2.26 microversion which added server tags to the server
GET response.
On 7/14/2016 3:11 AM, GHANSHYAM MANN wrote:
1. Always add a schema change to Tempest if a microversion changes a
response.
The problem with this is we shouldn't land a schema change by itself in tempest.
Until we have something using the schema we have no verification that they
actually work.
On Thu, Jul 14, 2016 at 12:08 PM, Matthew Treinish wrote:
> On Wed, Jul 13, 2016 at 09:55:33PM -0500, Matt Riedemann wrote:
>> There are several changes in Tempest right now trying to add response schema
>> validation for the 2.26 microversion which added server tags to the
Thanks Matt for bringing this up.
On Thu, Jul 14, 2016 at 11:55 AM, Matt Riedemann
wrote:
> There are several changes in Tempest right now trying to add response schema
> validation for the 2.26 microversion which added server tags to the server
> GET response. This
Hi Matt,
2016-07-14 11:55 GMT+09:00 Matt Riedemann :
> There are several changes in Tempest right now trying to add response schema
> validation for the 2.26 microversion which added server tags to the server
> GET response. This is needed for anything testing a
On Wed, Jul 13, 2016 at 09:55:33PM -0500, Matt Riedemann wrote:
> There are several changes in Tempest right now trying to add response schema
> validation for the 2.26 microversion which added server tags to the server
> GET response. This is needed for anything testing a microversion >=2.26,
>