RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

Backport this:

commit 55a8f8dc2e83b2c1484329f5a902dd6cea1b9cc6 (origin/use-logging, use-logging)
Author: Michal Domonkos <mdomonko>
Date:   Tue Nov 7 14:27:44 2017 +0100

    yumRepo: migrate more prints to logging
    
    Why these in particular?  Some of them are rather common in real life
    scenarios (remote repos going down etc.) and respecting errorlevel will
    make life easier for yum-cron users who choose to silence errors with
    debuglevel=-4 (yum-cron sets errorlevel = debuglevel + 4), such as to
    avoid getting emails after every repo failure.

GitHub PR:
https://github.com/rpm-software-management/yum/pull/58

These messages are still aggravating me in 7.5, and have been for years (see bz#1271287). Can we plesase get this really simple upstream fix backported to CentOS 7?

Yes, we are considering a backport to RHEL in the upcoming minor release, after which it should make it into CentOS as well.

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-2020:1122