Error messages returned to the user are not consistent across all apis

Bug #1459958 reported by Pranali Deore
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Low
Pranali Deore
OpenStack Compute (nova)
Opinion
Wishlist
Rajesh Tailor

Bug Description

Error messages returned to the user are not consistent across all apis in case of all exceptions derived from NotFound exception,
e.g., VolumeNotFound, SnapshotNotFound etc.

Tags: api
Changed in cinder:
assignee: nobody → Pranali Deore (pranali-deore)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

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

Changed in cinder:
status: New → In Progress
Jay Bryant (jsbryant)
Changed in cinder:
importance: Undecided → Low
Changed in cinder:
status: In Progress → Fix Committed
Changed in cinder:
milestone: none → liberty-2
status: Fix Committed → Fix Released
Changed in nova:
assignee: nobody → Rajesh Tailor (rajesh-tailor)
Revision history for this message
Rajesh Tailor (rajesh-tailor) wrote :

This issue is in nova project as well, where generic NotFound exception is raised instead of Specific NotFound exception.
for eg. InstanceNotFound, VolumeNotFound, ImageNotFound etc.

tags: added: api
Revision history for this message
Sean Dague (sdague) wrote :

I feel like this is one of those things where we need the API working group error specification and can move on from there. Pattern matching on exception names (which might change), isn't really a good long term plan.

Changed in nova:
status: New → Opinion
importance: Undecided → Wishlist
Thierry Carrez (ttx)
Changed in cinder:
milestone: liberty-2 → 7.0.0
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.