Bug 790187

Summary: Inconsistent handling of deleting non-existent things related to package groups
Product: [Retired] Pulp Reporter: Jay Dobies <jason.dobies>
Component: user-experienceAssignee: Todd Sanders <tsanders>
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:11:34 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 21:02:02 UTC 
Deleting a package group that doesn't exist results in a vague warning:

[jdob@pulp1 ~]$ pulp-admin packagegroup delete --repoid pulp-f16 --id foo
Unable to delete Packagegroup [foo] from repository [pulp-f16]

Deleting a package group category that doesn't exist shows a successful delete:

[jdob@pulp1 ~]$ pulp-admin packagegroup delete_category --repoid pulp-f16 --categoryid foo
Package group category [foo] deleted from repository [pulp-f16]

We should pick one behavior and stick with it, at least within the same section of commands (in this case, package groups).
Comment 86 Michael Hrivnak 2013-09-27 14:11:34 UTC 
These commands have changed drastically and no longer have this problem.