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.
This looks to be fixed in 6.2
here is a repo with a manually loaded rpm showing up in pulp-admin on a capsule
Id: Default_Organization-capsule_stuff-manual_upload
Display Name: manual_upload
Description: None
Content Unit Counts:
Rpm: 1
To test I used satellite-6.2.0-21.1.el7sat.noarch
1) Associated a capsule with Library environment
2) Created a new product without a URL
3) Manually uploaded an rpm to the product
4) Synced the capsule
5) Checked for the repo on the capsule
Id: Default_Organization-capsule_stuff-manual_upload
Display Name: manual_upload
Description: None
Content Unit Counts:
Rpm: 1
Repo is present with the manually uploaded rpm
Verified!
Satellite 6.3.0 snap 17
Steps:
1. Added Library lifecycle environment to the capsule
2. Created a new product
3. Added yum repository without specifying an URL
4. Manually uploaded an rpm file to the repository
5. Published CV having uploaded rpm to Library environment
Behavior:
1. As soon as CV is published to Library env containing uploaded rpm, the capsule sync is triggered automatically
2. Uploaded content is synced to capsule
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
For information on the advisory, and where to find the updated files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2018:0336