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