Bug 1477667 - cdn-sync --no-packages will disassociate all packages from channel
cdn-sync --no-packages will disassociate all packages from channel
Status: CLOSED ERRATA
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Satellite Synchronization (Show other bugs)
580
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Jan Dobes
Ales Dujicek
:
Depends On:
Blocks: sat58-errata
  Show dependency treegraph
 
Reported: 2017-08-02 11:18 EDT by Jan Dobes
Modified: 2017-09-06 08:27 EDT (History)
4 users (show)

See Also:
Fixed In Version: spacewalk-backend-2.5.3-145-sat
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-09-06 08:27:53 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jan Dobes 2017-08-02 11:18:00 EDT
Description of problem:
When cdn-sync is run with --no-packages, all existing packages in given channel(s) are disassociated. --no-packages should mean only to skip relevant stage during sync.

Version-Release number of selected component (if applicable):
spacewalk-backend-2.5.3-144

How reproducible:
always

Steps to Reproduce:
1. fully sync some channel using cdn-sync
2. run cdn-sync (for given channel) again with --no-packages option

Actual results:
All packages are gone from channel.

Expected results:
Packages will stay in channel.

Additional info:
Running cdn-sync again without --no-packages option will link all packages back to channel unless cdn-sync --clear-cache is executed in the meantime.
Comment 1 Jan Dobes 2017-08-02 12:24:27 EDT
fix in spacewalk.git(master):

47a9c1e26c0bcbcc12ea3a307a128cb399b07b7d
Comment 5 Radovan Drazny 2017-08-25 05:20:59 EDT
Re-verified with spacewalk-backend-2.5.3-151.el6sat.
Comment 6 errata-xmlrpc 2017-09-06 08:27:53 EDT
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, 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-2017:2645

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