Bug #3356

Make Plankton handle bad reqs correctly

Added by Stratos Psomadakis almost 11 years ago. Updated over 10 years ago.

Status:Assigned Start date:03/01/2013
Priority:High Due date:
Assignee:Kostas Papadimitriou % Done:


Category:Plankton Spent time: -
Target version:0.14.0


  1. kamaki image delete foo
    (503) SERVICE UNAVAILABLE serviceUnavailable (Unexpected error.)

plankton should return BadRequest for non-existent images, instead of a 503.

Related issues

related to Synnefo - Feature #3358: Single decorator for handling API calls, with proper logg... Closed 03/03/2013
related to Synnefo - Feature #3359: Report cloud faults properly across Synnefo Closed 03/03/2013
related to Synnefo - Bug #3360: Deleting an image from Plankton multiple times does not f... Closed 03/03/2013

Associated revisions

Revision 4fb602b1
Added by Christos Stavrakakis over 10 years ago

Fix plankton ItemNotFound exception

Plankton backend raised AssertionError when an Image was not found.
Change this to raise faults.ItemNotFound error. Temporary commit
until common API decorator is implemented.

Refs #3356


#1 Updated by Vangelis Koukis over 10 years ago

  • Category set to Plankton
  • Status changed from New to Assigned
  • Assignee set to Kostas Papadimitriou
  • Priority changed from Medium to High
  • Target version set to 0.14.0

#2 Updated by Vangelis Koukis over 10 years ago

This will be solved by implementing the long-needed #3358 properly.
Plankton should report proper cloud faults, like we should do across Synnefo.

Also available in: Atom PDF