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.
DescriptionJustin Sherrill
2020-01-08 15:17:38 UTC
Description of problem:
Content view publishing of the RHEL 8 appstream repository does not work properly. It does not actually copy non-modular rpms that are contained in the appstream repo (like git).
Version-Release number of selected component (if applicable):
6.7.0 (any snap)
How reproducible:
Always
Steps to Reproduce:
1. Sync RHEL 8 os and appstream
2. Publish it in a CV with no filters
3. Subscribe a system to the content view
4. Try to yum install git
Actual results:
git package is not available
Expected results:
git package is available
Additional info:
Note, that if you grep the generated primary.xml file for "<package ", you'll see far fewer rpms in the cv version than the 'Library' version. (~400 instead of ~5000)
This will require a katello change to properly pull in the 'fixed' data from pulp.
Comment 6pulp-infra@redhat.com
2020-01-08 16:01:45 UTC
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
Comment 7pulp-infra@redhat.com
2020-01-08 16:01:46 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 8Tanya Tereshchenko
2020-01-09 11:38:46 UTC
The issue happens when a repo has at least one module with no artifacts.
In case of Centos/RHEL 8, it's perl 5.26.
Another problem which this bug triggers is during removal of a module without artifacts - all rpms are removed from a repo. E.g. if you try to remove perl 5.26 module, all RPMs will be unassociated from a repo and it takes a lot of time (in case of centos repo ~1h) for the task to complete.
Comment 9Tanya Tereshchenko
2020-01-09 14:04:23 UTC
(In reply to Tanya Tereshchenko from comment #8)
> Another problem which this bug triggers is during removal of a module
> without artifacts - all rpms are removed from a repo. E.g. if you try to
> remove perl 5.26 module, all RPMs will be unassociated from a repo and it
> takes a lot of time (in case of centos repo ~1h) for the task to complete.
False alarm. Retested removal on the fresh box, it's fine.
The root cause for this BZ stays the same and correct.
Comment 10pulp-infra@redhat.com
2020-01-09 18:04:55 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 11pulp-infra@redhat.com
2020-01-09 18:31:36 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
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