Hide Forgot
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.
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.
This seems to have been fixed long ago.