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.
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.
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.