yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #53713
[Bug 1602044] [NEW] Update server tag return plain text in response body instead of empty
Public bug reported:
update server tag API (PUT /servers/{server_id}/tags/{tag}) return the
201 and 204 success code if tag is created or already exist
respectively.
But in former case, API return response body with plain text-
'{"code": "201 Created", "message": "<br /><br />\\n\\n\\n", "title":
"Created"}'
This is because it use webob.exc to generate 201. This kind of response
body will break while parsing the data for content type. Also this is
consistent with other nova API.
webob.Response is the right choice to generate 201 without content.
** Affects: nova
Importance: Undecided
Assignee: Ghanshyam Mann (ghanshyammann)
Status: New
** Changed in: nova
Assignee: (unassigned) => Ghanshyam Mann (ghanshyammann)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1602044
Title:
Update server tag return plain text in response body instead of empty
Status in OpenStack Compute (nova):
New
Bug description:
update server tag API (PUT /servers/{server_id}/tags/{tag}) return the
201 and 204 success code if tag is created or already exist
respectively.
But in former case, API return response body with plain text-
'{"code": "201 Created", "message": "<br /><br />\\n\\n\\n", "title":
"Created"}'
This is because it use webob.exc to generate 201. This kind of
response body will break while parsing the data for content type. Also
this is consistent with other nova API.
webob.Response is the right choice to generate 201 without content.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1602044/+subscriptions
Follow ups