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:
Drpms are synced ok but not copied over during content view publish
Version-Release number of selected component (if applicable): 6.6 maybe 6.7
How reproducible: always
Steps to Reproduce:
1. Create a repo with feed pointing to http://mirrors.oit.uci.edu/centos/7.6.1810/extras/x86_64/
2. Sync
3. Get the backend identifier fomr the repo details
4. ls /var/lib/pulp/published/yum/master/yum_distributor/<identifier>/...
you should see something like
drpms/ Packages/ repodata/
5. Now add this repo to a content view and publish
6.
ls /var/lib/pulp/published/yum/master/yum_distributor/<org>-<cv>-Library-<backend identifier>/...
Actual results:
Packages/ repodata/
Note none of the drpms got to the environment.
Expected results:
drpms/ Packages/ repodata/
Additional info:
Steps to test:
1. Create a repo with feed pointing to http://mirrors.oit.uci.edu/centos/7.6.1810/extras/x86_64/
2. Sync
3. Get the backend identifier fomr the repo details
4. ls /var/lib/pulp/published/yum/master/yum_distributor/<identifier>/...
you should see something like
drpms/ Packages/ repodata/
5. Now add this repo to a content view and publish
6. ls /var/lib/pulp/published/yum/master/yum_distributor/<org>-<cv>-Library-<backend identifier>/...
Actual results:
drpms/ Packages/ repodata/
Note none of the drpms got to the environment.
Expected results:
drpms/ Packages/ repodata/
Additional note: I also drilled into the drpms to verified that contents are populated in that dir and it does indeed.
Verified on 6.7.0_15
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-2020:1454