Bug 1507553

Summary:	[RFE] Remove error messages about channels not being mapped unless user runs cdn-sync with verbose option
Product:	Red Hat Satellite 5	Reporter:	Candace Sheremeta <cshereme>
Component:	Satellite Synchronization	Assignee:	Jan Dobes <jdobes>
Status:	CLOSED ERRATA	QA Contact:	Martin Korbel <mkorbel>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	580	CC:	ggainey, kdixon, mkorbel, rjerrido, tlestach, xdmoon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	spacewalk-backend-2.5.3-161-sat	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-06 15:46:27 UTC	Type:	Bug
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:	1450111

Description Candace Sheremeta 2017-10-30 14:46:34 UTC

Description of problem:
After upgrading to Satellite 5.8 from some previous version of Satellite 5.x, if the user had channels synced on the previous version that are not mapped to the CDN (due to the channel being deprecated, etc), the user will see error messages like the following when running a cdn-sync:

23:43:56 ERROR: Channel 'rhel-x86_64-server-lb-6.3.z-debuginfo' not found in channel metadata mapping.
23:43:57 ERROR: Channel 'redhat-rhn-proxy-5.6-server-x86_64-5' not found in channel metadata mapping.
23:43:58 ERROR: Channel 'rhel-x86_64-server-6.3.z' not found in channel metadata mapping.
23:43:58 ERROR: Channel 'rhel-x86_64-server-optional-6.3.z' not found in channel metadata mapping.
23:43:59 ERROR: Channel 'rhn-tools-rhel-x86_64-server-6.3.z' not found in channel metadata mapping.
23:43:59 ERROR: Channel 'rhel-x86_64-server-supplementary-6.3.z' not found in channel metadata mapping.
23:43:59 ERROR: Channel 'rhel-x86_64-server-6.3.z-debuginfo' not found in channel metadata mapping.
23:43:59 ERROR: Channel 'redhat-rhn-proxy-5.3-server-x86_64-5' not found in channel metadata mapping.

As these error messages can be safely ignored, we would kindly request that they not show up in the output of cdn-sync unless the user runs cdn-sync with the verbose option. Support Delivery is handling innumerable cases where customers are concerned about these "error" messages wherein we have to tell them that these messages can be safely ignored.

Version-Release number of selected component (if applicable):
Satellite 5.8 (after upgrading from previous version of Satellite 5.x)

How reproducible:
100%

Steps to Reproduce:
1. Build a Satellite 5.7 or lower
2. Sync a channel on the Satellite that is not currently mapped to the CDN (see above list for examples)
3. Upgrade Satellite to 5.8 and run cdn-sync

Actual results:
Error message appears for channel that is not mapped to CDN

Expected results:
We would like for this error message to not appear unless the user runs cdn-sync with the verbose option

Comment 4 Jan Dobes 2018-01-08 10:56:18 UTC

changed error message verbosity in spacewalk.git(master):

b17473bca3fa924ce0e6b42e6ab9b50358961724

support listing such unmapped channels:

29da981cd71482139aadcd11aa5336d945ea445d

Comment 7 Martin Korbel 2018-02-22 10:10:59 UTC

VERIFIED on spacewalk-backend-2.5.3-161

Reproducer in comment #0


Old version:
>cdn-sync
05:03:11 ERROR: Channel 'rhel-x86_64-server-6.3.z' not found in channel metadata mapping.
05:03:11 ======================================
05:03:11 | Channel: rhel-x86_64-server-6
05:03:11 ======================================
05:03:11 Sync of channel started.


New version:
> cdn-sync
05:07:34 ======================================
05:07:34 | Channel: rhel-x86_64-server-6
05:07:34 ======================================
05:07:34 Sync of channel started.

Comment 10 errata-xmlrpc 2018-03-06 15:46:27 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-2018:0393