Stack Update API doesn't return an useful response.

Bug #1336729 reported by Masahito Muroi on 2014-07-02
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Triaged
Low
Shashwat Srivastava

Bug Description

Stack update API return a response which just means "the request is accepted".

<html>
 <head>
  <title>202 Accepted</title>
 </head>
 <body>
  <h1>202 Accepted</h1>
  The request is accepted for processing.<br /><br />

 </body>
</html>

So stack-update api should return a json response like stack create API.

Changed in heat:
assignee: nobody → Masahito Muroi (muroi-masahito)
Thomas Herve (therve) wrote :

It's not clear why. What are you expecting it to return?

Changed in heat:
status: New → Incomplete
Masahito Muroi (muroi-masahito) wrote :

At least I expect a json style response when I call stack update API with json body.

Steve Baker (steve-stevebaker) wrote :

A 202 status code with no response body seems appropriate for this API call. I can think of nothing the body needs to return which isn't already known.

It is quite legitimate for REST API calls to only return a status code.

Masahito Muroi (muroi-masahito) wrote :

I agree no response body is better than HTML response too.

How about changing this response body to nothing?

Fix proposed to branch: master
Review: https://review.openstack.org/108975

Changed in heat:
status: Incomplete → In Progress
Zane Bitter (zaneb) wrote :

The content encoding is determined by the "Accept" header of the request, not the "Content-Type". Although we're not actually looking at that, I'm not sure how returning no data is better than returning data that the caller doesn't have to look at but which can make e.g. debugging in a browser easier/possible.

On 23/07/14 10:30, Zane Bitter wrote:
> The content encoding is determined by the "Accept" header of the
> request, not the "Content-Type". Although we're not actually looking at
> that, I'm not sure how returning no data is better than returning data
> that the caller doesn't have to look at but which can make e.g.
> debugging in a browser easier/possible.
>
I'm not against returning body content if it is actually useful to
someone, I was just saying that returning only a status code is valid REST.

Angus Salkeld (asalkeld) on 2015-01-06
Changed in heat:
importance: Undecided → Low
Changed in heat:
status: In Progress → Triaged

Will try to fix to unit case for this.
Taking over

Changed in heat:
assignee: Masahito Muroi (muroi-masahito) → Shashwat Srivastava (shashwat-srivastava)
Zane Bitter (zaneb) on 2016-05-26
Changed in heat:
assignee: Shashwat Srivastava (shashwat-srivastava) → nobody
assignee: nobody → Shashwat Srivastava (shashwat-srivastava)

Change abandoned by Masahito Muroi (<email address hidden>) on branch: master
Review: https://review.openstack.org/108975

Rico Lin (rico-lin) on 2018-05-07
Changed in heat:
milestone: none → no-priority-tag-bugs
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers