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.

Bug 1515530

Summary: RFE -Intersatellite sync of Content Views
Product: Red Hat Satellite Reporter: Jesse Triplett <jtriplet>
Component: Inter Satellite SyncAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: bbuckingham, dcaplan
Target Milestone: UnspecifiedKeywords: PrioBumpPM
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-01 13:51:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jesse Triplett 2017-11-21 02:21:23 UTC 
While syncing packages from one satellite to another if valuable, having to move back and forth content views and other system content meta data makes the current feature set unscalable.

The purpose of this request is to allow content views and other valuable data to be inter satellite synced between installations.

In this use case, the DEV and Prod environments are strictly separated which necessitates having multiple installations of Satellite 6. (One for DEV and one for PROD) one tens of thousands of systems are managed, having to manually (by hand or with scripts) export content views from one satellite only to import into another generates a large overhead in the amount of work needed for the workflow to be complete.
Comment 3 Brad Buckingham 2017-12-01 13:51:18 UTC 
Thank you for the bugzilla report.  This appears to be a duplicate of bug 1269273; therefore, I am going to mark it as duplicate.  If that is not the case, please feel free to re-open with the appropriate details.

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