Bug 528227

Summary:	Sat-sync with a different org it will remove the first.
Product:	Red Hat Satellite 5	Reporter:	Brandon Perkins <bperkins>
Component:	Satellite Synchronization	Assignee:	Milan Zázrivec <mzazrivec>
Status:	CLOSED ERRATA	QA Contact:	Jan Hutař <jhutar>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	530	CC:	cperry, jhutar, jkastner, xdmoon
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	533018 (view as bug list)		Environment:
Last Closed:	2009-12-16 13:46:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	518256

Description Brandon Perkins 2009-10-09 21:16:42 UTC

Description of problem:
Sat-sync with a different org it will remove the first.

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.
2. Run satellite-sync against one org then run the identical one against a second org.
  
Actual results:
The channel association flips from the first org to the second org.  It will continue to flip-flop as the commands are run associating with whichever org is indicated last.

Expected results:
One of:
1) Warning about the flip-flop.
2) Preventing the change of orgs altogether.
3) Satellite sync should allow syncing content to multiple orgs:   Bug 528226 -  Satellite sync should allow syncing content to multiple orgs.


Additional info:

Comment 1 Brandon Perkins 2009-10-09 21:20:02 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 6 Milan Zázrivec 2009-11-04 17:20:52 UTC

Syncing one channel into two different organizations is not an easy task
to do: currently the 5.3.0 schema wouldn't support it -> not something
that can be accomplished in 5.3.1 release.

What I decided to do is to have satellite-sync print a warning in case
the process would move previously synced channel in between organizations.

Example:

08:17:03 WARNING: Channel test-channel is already present in orgid 22.
08:17:03          Running synchronization will move the channel to orgid 2.

spacewalk.git master: 4187a6950eeebf51aee2ca73e3810c392fb47580
satellite.git SATELLITE-5.3: 3f0590fbc1689b7f31511c03117699aaefb1932c

Comment 7 Michael Mráka 2009-11-13 08:25:04 UTC

Package spacewalk-backend-0.5.28-35 was pushed to webQA. Moving ON_QA.

Comment 10 errata-xmlrpc 2009-12-16 13:46:58 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-1683.html