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