Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1239077 - Cannot rename product back to original name after importing a manifest
Cannot rename product back to original name after importing a manifest
Status: CLOSED WONTFIX
Product: Red Hat Satellite 6
Classification: Red Hat
Component: API (Show other bugs)
6.0.8
Unspecified Unspecified
unspecified Severity high (vote)
: GA
: Unused
Assigned To: Tom McKay
Katello QA List
: ReleaseNotes, Triaged
: 1238638 (view as bug list)
Depends On:
Blocks: sat61-release-notes
  Show dependency treegraph
 
Reported: 2015-07-03 08:40 EDT by Justin Sherrill
Modified: 2018-03-22 13:53 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-03-22 13:53:51 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Justin Sherrill 2015-07-03 08:40:55 EDT
Version-Release number of selected component (if applicable):
6.0.8 and 6.1.0


How reproducible:
always

Steps to Reproduce:
1.  Create a product named 'foo' in a new org
2.  Import a manifest 
3.  Rename the product to 'bar'
4.  Attempt to rename the product back to 'foo'

Actual results:
Error:

  Validation failed: Name Product with name 'foo' already exists in this organization.



Expected results:

product renames successfully.


Additional info:


A workaround would be to do this:

# foreman-rake console
> Katello::MarketingProduct.find_by_name('foo').destroy

and then rename again.  Notice that the problem may come back as soon as you import or refresh a manifest
Comment 2 Brad Buckingham 2015-07-07 13:21:53 EDT
*** Bug 1238638 has been marked as a duplicate of this bug. ***
Comment 5 David O'Brien 2016-04-17 20:47:57 EDT
Reset docs contact <> daobrien
Comment 7 Bryan Kearney 2018-03-22 13:53:51 EDT
The work around code no longer exists in the product, so I am assuming this is no longer an issue. I am closing this out as WONTFIX. If you are still seeing this issue please feel free to re-open with additional information.

Note You need to log in before you can comment on or make changes to this bug.