Bug 790137

Summary: No matching packages incorrectly marked as an error
Product: [Retired] Pulp Reporter: Jay Dobies <jason.dobies>
Component: user-experienceAssignee: Todd Sanders <tsanders>
Status: CLOSED WORKSFORME QA Contact: Preethi Thomas <pthomas>
Severity: low Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: mhrivnak, tsanders
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-27 13:58:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jay Dobies 2012-02-13 18:09:23 UTC 
When running a package search with no matches, the client reports the result as an error. It's misleading since that's not an error condition, it simply means there are no matching results, yet as a user it would indicate that the Pulp server ran into a problem attempting to perform the search.

Low priority but should also be a pretty quick fix. The only potential caveat would be if the REST API were raising an error instead of returning an empty list, which if that's the case is definitely a bug in its own right.

Example:

[jdob@pulp1 ~]$ pulp-admin package search -a i386
error:  No packages found.
Comment 1 Jay Dobies 2012-02-13 18:13:47 UTC 
Along the same lines, the exit code from that call indicates an error took place. That's more disconcerting than just the mislabeled message to the user. This can cause problems for users attempting to script a series of calls.
Comment 87 Michael Hrivnak 2013-09-27 13:58:25 UTC 
This seems to have been fixed long ago.