Bug 1459878 - cdn-sync: syncing into custom channel will unlink packages but not errata
Summary: cdn-sync: syncing into custom channel will unlink packages but not errata
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Satellite Synchronization
Version: 580
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Dobes
QA Contact: Lukáš Hellebrandt
Martin Korbel
URL:
Whiteboard:
Depends On:
Blocks: sat58-errata
TreeView+ depends on / blocked
 
Reported: 2017-06-08 12:37 UTC by Jan Dobes
Modified: 2017-10-19 11:57 UTC (History)
3 users (show)

Fixed In Version: spacewalk-backend-2.5.3-152-sat
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-19 11:57:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2915 0 normal SHIPPED_LIVE Red Hat Satellite 5.8.0 bug fix update 2017-10-19 15:56:50 UTC

Description Jan Dobes 2017-06-08 12:37:30 UTC
Description of problem:
When we implemented cdn-sync, we decided to not support unlinking errata from channels after they are once imported (satellite-sync doesn't support it either). But for syncing into custom channels (where repositories can be dynamically added/deleted) it would make sense.

Steps to Reproduce:
1. Create custom channel
2. assign repository to channel using cdn-sync -c <channel> -a <repo>
3. un-assign repository from channel using cdn-sync -c <channel> -d <repo>

Actual results:
Packages from channel are unlinked but errata are still there.

Expected results:
Errata should be unlinked from channel too.

Comment 1 Jan Dobes 2017-08-07 15:31:24 UTC
fixed in spacewalk.git(master):

bbfb9945a31624b9cddfaf71c39f067640840357

Comment 4 Martin Korbel 2017-09-20 11:44:41 UTC
Verified on spacewalk-backend-2.5.3-152

Reproducer in comment #0

Comment 6 errata-xmlrpc 2017-10-19 11:57:19 UTC
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/RHBA-2017:2915


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