> > > > > > 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. > > +1. As you know, neutron also implemented strict validation in Rocky but with > discovery via config option and extensions mechanism. Same way Cinder should > make it with backward compatible way till 3.53 version. >
I agree. I _thought_ that was the way it was implemented, but apparently something was missed. I will try to look at this soon and see what would need to be changed to get this behaving correctly. Unless someone else has the time and can beat me to it, which would be very much appreciated. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev