Duplicate location error should raise HTTPConflict

Bug #1520053 reported by wangxiyuan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Glance
In Progress
Medium
Unassigned

Bug Description

When add or replace a duplicate location to an image, Glance should raise 409 HTTPConflict, not 400 HTTPBadRequest.

The glance client raise 409, we should keep the same with the client.

wangxiyuan (wangxiyuan)
Changed in glance:
assignee: nobody → wangxiyuan (wangxiyuan)
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to glance (master)

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

Changed in glance:
status: New → In Progress
Revision history for this message
Niall Bunting (niall-bunting) wrote :

Confirmed that a 400 is returned.

Revision history for this message
Flavio Percoco (flaper87) wrote :

I'm afraid changing this would be considered a breaking change as it'll change the return code from the API. I don't think we'll be able to "fix" this

Changed in glance:
importance: Undecided → Medium
Revision history for this message
wangxiyuan (wangxiyuan) wrote :

Then I have no idea what to do next. I totally think that Duplicate error should return 409. And the glance client returned 409. Any suggestion? :(

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on glance (master)

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

wangxiyuan (wangxiyuan)
Changed in glance:
assignee: wangxiyuan (wangxiyuan) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.