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:
python3-pulp_manifest, the RPM that is used to generate the PULP_MANIFEST file for file repositories, is missing from the Satellite client repositories. It should be available so hosts can install the RPM and create Pulp-compatible file repositories. 

This part of the documentation is related: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html/managing_content/managing_custom_file_type_content_content-management#Creating_a_Remote_File_Type_Repository_content-management

Version-Release number of selected component (if applicable):

Satellite 6.11+

How reproducible:
Always


Steps to Reproduce:
1. Enable + sync satellite-client-6-for-rhel-8-x86_64-rpms
2. See that python3-pulp_manifest is missing


Additional info:

This BZ was reported for the same issue against 6.10: https://bugzilla.redhat.com/show_bug.cgi?id=1996075

Closing this as a duplicate, the issue already has BZs for 6.11 and 6.12.

*** This bug has been marked as a duplicate of bug 2122205 ***