Bug 1120315 - satellite-sync will not work between ISS servers without specifying channel
Summary: satellite-sync will not work between ISS servers without specifying channel
Keywords:
Status: CLOSED EOL
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 2.1
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-16 17:43 UTC by Carl Thompson
Modified: 2019-10-21 11:50 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-21 11:50:51 UTC
Embargoed:


Attachments (Terms of Use)

Description Carl Thompson 2014-07-16 17:43:01 UTC
Description of problem:
When running satellite-sync on a slave ISS server it will not syncronize channels that have been previously syncronized without specifying channels

Version-Release number of selected component (if applicable):
spacewalk 2.1

How reproducible:
Every time

Steps to Reproduce:
1. Setup master/slave ISS configuration and export org with channels to slave
2. Run initial satellite-sync -c to syncronize channel
3. Run satellite-sync without flags and you will receive an error

Actual results:
ERROR: No channels currently imported; try satellite-sync --list-channels; then satellite-sync -c chn0 -c chn1...

Expected results:
It would mark any previously syncronized servers as previously imported when initial import is done so that all previously imported channels will sync with a satellite-sync execution.

Additional info:

Comment 1 Michael Mráka 2019-10-21 11:50:51 UTC
Spacewalk 2.8 (and older) has already reached it's End Of Life.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before end of life. If you would still like
to see this bug fixed and are able to reproduce it against current version
of Spacewalk 2.9, you are encouraged change the 'version' and re-open it.


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