On Wed, Aug 08, 2018 at 05:15:26PM +0000, Sean McGinnis wrote: > On Tue, Aug 07, 2018 at 05:27:06PM -0500, Monty Taylor wrote: > > On 08/07/2018 05:03 PM, Akihiro Motoki wrote: > > >Hi Cinder and API-SIG folks, > > > > > >During reviewing a horizon bug [0], I noticed the behavior of Cinder API > > >3.0 was changed. > > >Cinder introduced more strict schema validation for creating/updating > > >volume encryption type > > >during Rocky and a new micro version 3.53 was introduced[1]. > > > > > >Previously, Cinder API like 3.0 accepts unused fields in POST requests > > >but after [1] landed unused fields are now rejected even when Cinder API > > >3.0 is used. > > >In my understanding on the microversioning, the existing behavior for > > >older versions should be kept. > > >Is it correct? > > > > I agree with your assessment that 3.0 was used there - and also that I would > > expect the api validation to only change if 3.53 microversion was used. > > > > I filed a bug to track this: > > https://bugs.launchpad.net/cinder/+bug/1786054 >
Sorry, between lack of attention to detail (lack of coffee?) and an incorrect link, I think I went down the wrong rabbit hole. The change was actually introduced in [0]. I have submitted [1] to allow the additional parameters in the volume type encryption API. This was definitely an oversight when we allowed that one through. Apologies for the hassle this has caused. [0] https://review.openstack.org/#/c/561140/ [1] https://review.openstack.org/#/c/590014/ __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
