Bug 790170

Summary: No package groups in a repository is incorrectly flagged as an error
Product: [Retired] Pulp Reporter: Jay Dobies <jason.dobies>
Component: user-experienceAssignee: John Matthews <jmatthew>
Status: CLOSED WORKSFORME QA Contact: Preethi Thomas <pthomas>
Severity: unspecified 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 14:05:44 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 20:10:55 UTC 
This is similar to 790137.

When listing package groups in a repository, the lack of any is not an error condition, it's simply the state of the repository. This is reflected in the client in both the command output [1] and the exit code [2].

The bigger concern here, as with 790137, is if the REST API incorrectly indicates an error instead of returning an empty list. This needs to be checked in the fixing of this bug as well.

[1]

[jdob@pulp1 ~]$ pulp-admin packagegroup list --repoid pulp-f16
error:  No package groups found in repo [pulp-f16]


[2]

[jdob@pulp1 ~]$ echo $?
65
Comment 1 Michael Hrivnak 2013-09-27 14:05:44 UTC 
this is no longer an issue