Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 805709 - Package filter name is unique to entire system
Summary: Package filter name is unique to entire system
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Justin Sherrill
QA Contact: Og Maciel
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-21 21:10 UTC by Og Maciel
Modified: 2019-09-26 15:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Package filter restrictions for unique filter names were System Engine-wide. This prevented filters with the same function but set to different organizations from duplicating in name. This fix removes this restriction and makes the filter name unique within the organization. Package filters now share the same name provided they are in different organizations.
Clone Of:
Environment:
Last Closed: 2012-12-04 19:43:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Script to reproduce this. (1.75 KB, application/x-shellscript)
2012-03-21 21:10 UTC, Og Maciel 		no flags Details
Adding package filter via the web ui (91.32 KB, image/png)
2012-03-21 21:11 UTC, Og Maciel 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1543 0 normal SHIPPED_LIVE Important: CloudForms System Engine 1.1 update 2012-12-05 00:39:57 UTC

Description Og Maciel 2012-03-21 21:10:49 UTC 
Created attachment 571855 [details]
Script to reproduce this.

Description of problem:

I'm not sure if this is a pulp bug or not, so please move it appropriately. Using the katello cli to create orgs, products and repos, I noticed that the filter name is not unique to an Organization or even to a product, but to the entire SE. I'm not sure why we have this strictiness for filter names, but I'd make the case that one should be able to use the same name for a filter if they're associated with different organizations. See attached script for instructions on how to test.

Version-Release number of selected component (if applicable):

* candlepin-0.5.26-1.el6.noarch
* candlepin-tomcat6-0.5.26-1.el6.noarch
* katello-0.1.305-1.el6.noarch
* katello-all-0.1.305-1.el6.noarch
* katello-candlepin-cert-key-pair-1.0-1.noarch
* katello-certs-tools-1.0.4-1.el6.noarch
* katello-cli-0.1.105-1.el6.noarch
* katello-cli-common-0.1.105-1.el6.noarch
* katello-common-0.1.305-1.el6.noarch
* katello-configure-0.1.106-1.el6.noarch
* katello-glue-candlepin-0.1.305-1.el6.noarch
* katello-glue-foreman-0.1.305-1.el6.noarch
* katello-glue-pulp-0.1.305-1.el6.noarch
* katello-qpid-broker-key-pair-1.0-1.noarch
* katello-qpid-client-key-pair-1.0-1.noarch
* katello-selinux-0.1.9-1.el6.noarch
* pulp-1.0.0-5.el6.noarch
* pulp-admin-1.0.0-5.el6.noarch
* pulp-client-lib-1.0.0-5.el6.noarch
* pulp-common-1.0.0-5.el6.noarch
* pulp-selinux-server-1.0.0-5.el6.noarch

How reproducible:


Steps to Reproduce:
1. Run the attached script.
2. Also try to create 2 package filters with the same name inside 2 different organizations using the web ui
3.
  
Actual results:

The web ui returns the following error notification:

Pulp::Filter: 409 Conflict "A filter with the id, pulp-filter, already exists" (POST /pulp/api/filters/)

Expected results:

I should be able to create package filters with the same name on different orgs.
Additional info:
Comment 1 Og Maciel 2012-03-21 21:11:39 UTC 
Created attachment 571856 [details]
Adding package filter via the web ui

Adding package filter via the web ui
Comment 3 Justin Sherrill 2012-03-23 20:39:05 UTC 
fyi, the reason you can't rename it or have two with the same name is because package filters store their name as the pulp id.  I have no idea why it was done this way, but it was.   So either pulp would need to add a name field, or we would.
Comment 4 Justin Sherrill 2012-04-02 17:35:22 UTC 
katello commits.
57d68b027436658196dc0a82fd0a78abdfb905df
fbbb9814219a1e1fc0ae05c1562e62e09b844c15


this requires a schema change, so moving to 1.1 release.
Comment 6 Og Maciel 2012-09-14 21:41:15 UTC 
Verified using:

* candlepin-0.7.8-1.el6cf.noarch
* candlepin-selinux-0.7.8-1.el6cf.noarch
* candlepin-tomcat6-0.7.8-1.el6cf.noarch
* katello-1.1.12-7.el6cf.noarch
* katello-all-1.1.12-7.el6cf.noarch
* katello-candlepin-cert-key-pair-1.0-1.noarch
* katello-certs-tools-1.1.8-1.el6cf.noarch
* katello-cli-1.1.8-4.el6cf.noarch
* katello-cli-common-1.1.8-4.el6cf.noarch
* katello-common-1.1.12-7.el6cf.noarch
* katello-configure-1.1.9-3.el6cf.noarch
* katello-glue-candlepin-1.1.12-7.el6cf.noarch
* katello-glue-pulp-1.1.12-7.el6cf.noarch
* katello-qpid-broker-key-pair-1.0-1.noarch
* katello-qpid-client-key-pair-1.0-1.noarch
* katello-selinux-1.1.1-1.el6cf.noarch
* pulp-1.1.12-1.el6cf.noarch
* pulp-common-1.1.12-1.el6cf.noarch
* pulp-selinux-server-1.1.12-1.el6cf.noarch
Comment 8 errata-xmlrpc 2012-12-04 19:43:28 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-1543.html
Note You need to log in before you can comment on or make changes to this bug.