Project

General

Profile

Actions

Bug #12384

closed

capsule content - APIs have unfriendly response when Pulp Node not enabled

Added by Brad Buckingham about 9 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Category:
API
Target version:
Difficulty:
trivial
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Currently, if a user invokes any of the capsule content APIs for a capsule that does not have the 'Pulp Node' feature, they will see an error similar to the following:
"Couldn't find SmartProxy with id=1 [WHERE "features"."name" IN ('Pulp Node')]"

Ideally, the user shouldn't be presented with a DB 'where' clause as part of the response. In the past, we did have a message to indicate that the action could not be performed; however, it was lost with some refactoring and feature work.

Actions

Also available in: Atom PDF