Re: [openstack-dev] [nova] 422 status codes from API
On Thu, 25 Jul 2013 10:29:47 -0400 Sean Dague s...@dague.net wrote: Some new tempest tests have been showing up that push deeper into the Nova API, and popping out seem to be a lot of places where we are returning 422 status codes. 422 is WebDav reserved code, not in a proper HTTP spec (WebDAV; RFC 4918), and a lot of the other projects have purged it out of their APIs. It would be good to understand if we consider this a bug that should get fixed in v2 / a v2 oversight that gets fixed in v3 / or par for the course, as that gives us some guidance on what to land in tempest, and what we file bugs on for nova. Are these getting recorded anywhere currently? AFAIK we've been fixing all of them in the v3 porting effort, but it'd be nice to know before the H3 release if we missed anyway . Chris ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [nova] 422 status codes from API
Some new tempest tests have been showing up that push deeper into the Nova API, and popping out seem to be a lot of places where we are returning 422 status codes. 422 is WebDav reserved code, not in a proper HTTP spec (WebDAV; RFC 4918), and a lot of the other projects have purged it out of their APIs. It would be good to understand if we consider this a bug that should get fixed in v2 / a v2 oversight that gets fixed in v3 / or par for the course, as that gives us some guidance on what to land in tempest, and what we file bugs on for nova. -Sean -- Sean Dague http://dague.net ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] 422 status codes from API
Just as a data point, we considered these a *bug* in Cinder and fixed them as I recall. On Thu, Jul 25, 2013 at 8:29 AM, Sean Dague s...@dague.net wrote: Some new tempest tests have been showing up that push deeper into the Nova API, and popping out seem to be a lot of places where we are returning 422 status codes. 422 is WebDav reserved code, not in a proper HTTP spec (WebDAV; RFC 4918), and a lot of the other projects have purged it out of their APIs. It would be good to understand if we consider this a bug that should get fixed in v2 / a v2 oversight that gets fixed in v3 / or par for the course, as that gives us some guidance on what to land in tempest, and what we file bugs on for nova. -Sean -- Sean Dague http://dague.net __**_ OpenStack-dev mailing list OpenStack-dev@lists.openstack.**org OpenStack-dev@lists.openstack.org http://lists.openstack.org/**cgi-bin/mailman/listinfo/**openstack-devhttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] 422 status codes from API
On 07/25/2013 10:29 AM, Sean Dague wrote: Some new tempest tests have been showing up that push deeper into the Nova API, and popping out seem to be a lot of places where we are returning 422 status codes. 422 is WebDav reserved code, not in a proper HTTP spec (WebDAV; RFC 4918), and a lot of the other projects have purged it out of their APIs. It would be good to understand if we consider this a bug that should get fixed in v2 / a v2 oversight that gets fixed in v3 / or par for the course, as that gives us some guidance on what to land in tempest, and what we file bugs on for nova. I'm fine fixing it as a bug. This is called out as a change generally considered OK in the documented API change guidelines: https://wiki.openstack.org/wiki/APIChangeGuidelines -- Russell Bryant ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
