Bug 1377731

Summary: Creating product with same name as organization name breaks Satellite
Product: Red Hat Satellite Reporter: Jiri Vavra <jivavra>
Component: Content ManagementAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.1.9CC: bkearney, jivavra, ktordeur, mhulan, mklika
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-01 20:05:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jiri Vavra 2016-09-20 13:31:00 UTC 
Description of problem:
Creating product with same name as organization name breaks Satellite

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

How reproducible:
???

Steps to Reproduce:
1. Enable some Red Hat repositories under Content -> Red Hat Repositories (make sure you also sync them)
2. Add these to a new Content View
3. Create a new product with the same name as your organization
4. Add a repository to the product
5. Sync the repository to make sure there are some packages added
6. Add the product/repo to the Content View with the Red Hat repositories
7. Publish a new version to this Content View
8. Look at /var/log/foreman/production.log where it spits out a bunch of errors.
You will see all the Red Hat repositories are prefixed ORGANIZATION_NAME-REPO_NAME_HERE
This is why it will break when you add a product with the same name as your organization.

Actual results:
Broken Satellite

Expected results:
Working Satellite OR not to be able to name Product with same as organization

Additional info:
Customer provided steps to reproduce. I tried to reproduce it on my testing Satellite 6.1.9 and 6.2.1 but didn't succeed to break my Satellites.
Comment 1 Marek Hulan 2017-01-12 08:48:18 UTC 
Jiri I don't think the customer meant literally that the repository is prefixed with the string "ORGANIZATION_NAME-REPO_NAME_HERE" but with it real values. That's OK I think. I checked the attached production.log and I saw several conflicts and refused connections to postgres so there remained some tasks in pending state. It's likely that PG server was restarted during some operation so some tasks were paused but never resumed and now conflict with new tasks triggered by adding new repository. If customer still encounters some issues make sure they resumes/resolve or paused tasks first.
Comment 3 Bryan Kearney 2017-06-01 20:05:45 UTC 
We have not been able to recreate this bug. I am closing it out. If you continue to see this bug, please feel free to re-open this,