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:
Setting "update_messages=no" has no effect.  The messages will be emitted regardless.

The reason is that we only respect the update_messages value in a few places before emit*() calls but not in others.

We should fix this behavior according to the update_messages description that says:
# Whether a message should be emitted when updates are available,
# were downloaded, or applied.

One way would be to check for the value in the respective emit*() methods themselves (probably not all, just those related to downloading/updating) to make sure we catch all such occurrences.

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

How reproducible:
100%

Steps to Reproduce:
1. Make sure /etc/yum/yum-cron.conf contains the following:
  update_messages=no
  emit_via=stdio
  random_wait=0
3. Make sure there are updates available in the enabled repos
4. Run "yum-cron /etc/yum/yum-cron.conf"

Actual results:
The transaction is dumped to stdout, along with some informational messages.

Expected results:
No non-error messages should be printed.