This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .

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.

1) Proposed title of this feature request
 Enable synchronization and management of PyPI-type repositories in Red Hat Satellite.


2) What is the nature and description of the request?
- To sync PyPI-type repository so that all the content distribution servers and clients can have access to like other RHEL repositories.

3) How would the customer like to achieve this? (List the functional requirements here)
- To be able to sync/manage the PyPI-type repository to the Satellite server like other RHEL repositories.
- The upstream has already solved this - https://docs.theforeman.org/nightly/Managing_Content/index-katello.html#Managing_Python_Type_Content_content-management

4) Is there already an existing RFE upstream or in Red Hat Bugzilla?
- Yes, Red Hat Bugzilla id=1746508 but closed as WontFIX.

5) Does the customer have any specific timeline dependencies and which release would they like to target ?
- 6.15

6) Is the sales team involved in this request and do they have any additional input?
- No

7) Would the customer be able to assist in testing this functionality if implemented?
- Yes

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.