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.
Bug 1621038 - uploading a package to a repo, no Capsule sync is triggered
Summary: uploading a package to a repo, no Capsule sync is triggered
Keywords:
Status: CLOSED DUPLICATE of bug 1516803
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.3.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: vijsingh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-23 13:08 UTC by Pavel Moravec
Modified: 2023-03-24 14:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-23 13:39:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3578411 0 None None None 2018-08-23 13:22:16 UTC

Description Pavel Moravec 2018-08-23 13:08:48 UTC
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.

Comment 7 Pavel Moravec 2019-01-23 13:39:29 UTC
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 ***


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