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:

Syncable repository exports were added - https://bugzilla.redhat.com/show_bug.cgi?id=2069306
We need a way to import syncable exports. via
```
hammer content-import repository --organization=import-organization --path=<import>
```

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

Syncable import should
1) Auto Create the appropriate content view (unless it is library or repository)
2) Create any custom products and repositories
3) Enable any rh repositories
4) Update the sync urls of the repositories to point 'file://<dump location>/<repository path>'
5) Sync the repositories
6) Publish the content view

Connecting redmine issue https://projects.theforeman.org/issues/35505 from this bug

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35505 has been resolved.

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 (Important: Satellite 6.13 Release), 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-2023:2097

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days