Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Renaming a product causes an error:
Note that this doesn't occur with new products but only with old products.
When doing the following
1. Rename a product from NAME1 to NAME2
2. Rename the same product back from NAME2 to NAME2
You get the error
Product with name 'xxx' already exists in this organization
Customer ran some database queries to locate the Product.
It appears to be created in marketing_products
foreman=# select * from katello_products where name LIKE '%Openwave%';
id | name | description | cp_id | multiplier | provider_id | created_at | updated_at | gpg_key_id | type | sync_plan_id | label | organization_id
----+-----------+-------------+---------------+------------+-------------+----------------------------+----------------------------+------------+---------------------------+--------------+------------------------+-----------------
39 | Openwave | | 1431491295115 | | 4 | 2015-06-29 13:49:00.159878 | 2015-06-29 13:49:00.159878 | | Katello::MarketingProduct | | Openwave_1431491295115 | 3
34 | Openwave3 | | 1431491295115 | | 3 | 2015-05-13 04:28:14.849533 | 2015-07-02 04:07:26.908304 | 3 | Katello::Product | | Openwave | 3
(2 rows)
Is this bug resolved in 6.1 and if not, can we have a workaround?
Comment 1RHEL Program Management
2015-07-02 11:03:54 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.