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.

Created attachment 1324039 [details]
Output sample

Description of problem:
On some repos during loading the meta information an "!!!" mark is displayed.
But in the man page of yum there are no notes of it

Version-Release number of selected component (if applicable):
yum-3.4.3-150.el7

How reproducible:
Every time

Steps to Reproduce:
1. call yum update

Actual results:
On some repos the "!!!" mark is shown while downloading the meta information.

Expected results:
Some hint on this in the man page.


Additional info:
See the picture for the sample output.
Repo config for it:
[mariadb]
name=MariaDB Version 10.2
baseurl = https://yum.mariadb.org/10.2/rhel7-amd64
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mariadb

This is a cosmetic bug that appears whenever repo_gpgcheck=1 is used:

https://github.com/rpm-software-management/yum/issues/79

There is no plan to fix this bug during RHEL 7 life cycle.
If you still consider the issue important, please contact your support representative.