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:
Uploading a package to a custom repository in a custom product, the repo is properly published on Satellite. BUT the content does not get to Capsules associated to Library LE.
Version-Release number of selected component (if applicable):
Sat 6.3.2
How reproducible:
100%
Steps to Reproduce:
0. Have a Capsule associated to Library LE.
1. Create a custom repo (e.g. fed by https://repos.fedorapeople.org/repos/pulp/pulp/demo_repos/zoo/) in a custom product.
2. Sync the repo.
3. Check if the repo content is accessible for clients on Sat and on Capsule after a while.
4. Upload a package to the repo.
5. After a while, check if the uploaded package is available on Sat and Caps (i.e. run "yum list available uploaded-package --disablerepo=* --enablerepo=myCustomRepo" on a client registered to Sat and on another registered to Caps)
Actual results:
3. repo content available to either client
5. the package is available only to clients registered to Sat
Expected results:
5. the package avaialable also for the client registered to Caps
Additional info:
I think class in https://github.com/Katello/katello/blob/master/app/lib/actions/katello/repository/upload_files.rb needs to get a copy of method "run" from https://github.com/Katello/katello/blob/master/app/lib/actions/katello/repository/import_upload.rb - precisely executing the steps from that method is a workaround.
I realized this is a dup of (also mine) bz 1516803. Shame on me that I open two duplicate BZs.
I recently provided a fix for 1516803 to upstream, so that shall appear in Sat 6.6. It is trivial to backport - let discuss in that BZ if a sooner fix is requested (either as a z-stream ne or applying a standalone patch (that would be overwritten by next update, though).
*** This bug has been marked as a duplicate of bug 1516803 ***