Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
+++ This bug was initially created as a clone of Bug #999155 +++
Description of problem: I've got a large number of workstations that all have yum-cron enabled for package installation. I don't care if they installed the updates successfully - but I do care if they didn't.
I've attached a patch to allow you to only report errors with yum-cron
Version-Release number of selected component (if applicable): 3.4.3-106.fc19
How reproducible: 100%
Steps to Reproduce:
1. run yum-cron on a system where it errors
2. run yum-cron on a system where it succeeds
3. wish you could only get reports from #1
Actual results:
reporting always occurs
Expected results:
The ability to trim down what it reports to just systems with errors
Additional info:
A patch to add this behavior is attached.
--- Additional comment from Zdeněk Pavlas on 2013-08-26 07:40:05 EDT ---
http://lists.baseurl.org/pipermail/yum-devel/2013-August/010334.html
I've already written something similar, but this gets rid of more messages, and correctly handles the self.output==[] case, so I like it. Do you think that adding an extra option is better than just honoring the loglevel settings?
--- Additional comment from on 2013-08-26 09:06:01 EDT ---
Using loglevel for this seems great to me! Just need to make sure that the reduction in reporting is well documented so everyone knows how to get this behavior.
--- Additional comment from on 2013-10-21 15:50:55 EDT ---
Just checking back in, log_level seems like the right direction for this. Any hope of getting your patches at : http://lists.baseurl.org/pipermail/yum-devel/2013-August/010334.html merged?
I'd like to resolve this in the same way we did in Fedora, by new handling of yum-cron.conf options. Previously update_messages=NO acted as a master switch, turning off anything but updating the metadata cache. Backporting these two commits should be enough:
commit 587288e13575b6f3f6c8cdc1a13abe9117444636
Author: Zdenek Pavlas <zpavlas>
Date: Fri Oct 11 09:28:57 2013 +0200
yum-cron: support download/install with update_messages==False. BZ 1018068
(download_updates or apply_updates) now implies that yum-cron should
do the updates processing, too. The update_messages==False case is
then used to make yum-cron less chatty.
commit e1db5d6a94dee861d1fa0552277bc03f037c6e3a
Author: Zdenek Pavlas <zpavlas>
Date: Tue Dec 10 08:47:48 2013 +0100
yum-cron: stderr/email: no output if no messages
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.