Duplicated lease name should return HTTP 409 Conflict instead of HTTP 500

Bug #1302584 reported by Michał Kamiński
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Blazar
Fix Released
Medium
Michał Kamiński

Bug Description

Currently when user tries to create a lease with duplicated name,

Error
HTTP/1.1 500 INTERNAL SERVER ERROR {"error_name": 500, "error_message": "ClimateDBDuplicateEntry: A database error occurred", "error_code": 500} is presented, but should return

HTTP 409 CONFLICT
 {"error_name": "Duplicated Lease Name", "error_message": "Lease with name %lease_name already exists", "error_code": 409}

Dina Belova (dbelova)
Changed in climate:
status: New → Confirmed
importance: Undecided → Medium
Changed in climate:
assignee: nobody → Michał Kamiński (michal-kaminski)
Changed in climate:
status: Confirmed → In Progress
Revision history for this message
Michał Kamiński (michal-kaminski) wrote :

Fix proposed to branch: master
Review: https://review.openstack.org/#/c/85678/

Revision history for this message
Michał Kamiński (michal-kaminski) wrote :

(09:44:55) openstackgerrit: A change was merged to stackforge/climate: Duplicated lease name should return HTTP 409 https://review.openstack.org/85678

Changed in climate:
status: In Progress → Fix Committed
Changed in blazar:
milestone: none → 0.1.1
Changed in blazar:
status: Fix Committed → Fix Released
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.