Open Stack

500 error is bad for any API. IMO, I'm OK to fix it Mitaka. Deprecated
means that it could be dropped soon. It doesn't mean that it's not working
at all.

BTW, XML API almost has no tests so I'm not surprised that it's broken

Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/

On Fri, Jan 15, 2016 at 10:08 AM, Michał Dulko <michal.dulko at intel.com>
wrote:

> On 01/15/2016 07:14 AM, Jethani, Ravishekar wrote:
> > Hi Devs,
> >
> > I have come across a few 500 response issues while sending request
> > body as XML to cinder service. For example:
> >
> > <snip!>
> >
> > I can see that XML support has been marked as depricated and will be
> > removed in 'N' release. So is it still worth trying fixing these
> > issues during Mitaka time frame?
> >
> > Thanks.
> > Ravi Jethani
>
> One of the reasons XML API was deprecated is the fact that it weren't
> getting much CI testing and as Doug Hellmann once mentioned - "if
> something isn't tested then it isn't working".
>
> I'm okay with fixing it (if someone really needs that feature), but we
> don't have any means to prevent further regressions, so it may not be
> worth it.
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160115/d2288b00/attachment.html>