Re: [openstack-dev] [cinder] Should we fix XML request issues?

2016-01-15 Thread Doug Hellmann
Excerpts from Michał Dulko's message of 2016-01-15 09:08:54 +0100: > 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: > > > > > > > > I can see that XML

Re: [openstack-dev] [cinder] Should we fix XML request issues?

2016-01-15 Thread Sean McGinnis
On Fri, Jan 15, 2016 at 09:08:54AM +0100, Michał Dulko 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: > > > > > > > > I can see that XML

Re: [openstack-dev] [cinder] Should we fix XML request issues?

2016-01-15 Thread Ivan Kolodyazhny
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

Re: [openstack-dev] [cinder] Should we fix XML request issues?

2016-01-15 Thread Michał Dulko
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: > > > > I can see that XML support has been marked as depricated and will be > removed in 'N' release. So is it

[openstack-dev] [cinder] Should we fix XML request issues?

2016-01-14 Thread Jethani, Ravishekar
Hi Devs, I have come across a few 500 response issues while sending request body as XML to cinder service. For example: -- openstack@openstack-136:/opt/stack/cinder$ curl -i -X PUT -H "X-Auth-Token: 79e6f8f529d2494b81dbd1a6ea5e077d" -H "Accept: application/xml"