Bug 528226 - Satellite sync should allow syncing content to multiple orgs.
Summary: Satellite sync should allow syncing content to multiple orgs.
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Satellite Synchronization
Version: 530
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Milan Zázrivec
QA Contact: Jiri Kastner
URL:
Whiteboard:
Depends On:
Blocks: 462714 533018
TreeView+ depends on / blocked
 
Reported: 2009-10-09 21:10 UTC by Brandon Perkins
Modified: 2014-07-04 13:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-04 13:29:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Brandon Perkins 2009-10-09 21:10:20 UTC
Description of problem:
Satellite sync should allow syncing content to multiple orgs.

Version-Release number of selected component (if applicable):
spacewalk-backend-tools-0.5.28-34.el4sat

How reproducible:
Always.

Steps to Reproduce:
1. Setup Inter-Satellite-Sync.
2a. Run satellite-sync including two orgs, or
3b. Run satellite-sync against one org then run the identical one against a second org.
  
Actual results:
Only one org can consume the content.

Expected results:
More than one orgs can consume the content.

Additional info:

Comment 1 Brandon Perkins 2009-10-09 21:19:59 UTC
All related bugs that probably should be considered together when thinking about what to do:

Bug 528226 -  Satellite sync should allow syncing content to multiple orgs.
Bug 528227 -  Sat-sync with a different org it will remove the first.
Bug 528228 -  Sat-sync with two --org options will use the second.

Comment 2 Brandon Perkins 2009-10-09 21:31:54 UTC
Potentially of interest:

http://post-office.corp.redhat.com/archives/rhn-satellite/2009-October/msg00030.html

Comment 3 Milan Zázrivec 2009-11-04 17:29:58 UTC
Syncing the same content to multiple organizations is not an easy task.

Currently (Satellite 5.3.0) the schema would not allow us to have two
channels with the same label (regardless of which organization these
channels are created in) and allowing unique channel label per organization
could have large impacts on many other parts of the code: multiorg & channel
trusts for example ...

I'm removing this from under sat531-triage since this is not something
that can be accomplished without schema change.


Note You need to log in before you can comment on or make changes to this bug.