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.
Bug 1645618 - yum-cron message directs the user to use --verbose but does not offer the command to use it on
Summary: yum-cron message directs the user to use --verbose but does not offer the com...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: yum
Version: 7.5
Hardware: All
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Packaging Maintenance Team
QA Contact: Jan Blazek
URL:
Whiteboard:
Depends On:
Blocks: 1630909
TreeView+ depends on / blocked
 
Reported: 2018-11-02 16:18 UTC by Peter Portante
Modified: 2021-05-19 17:48 UTC (History)
5 users (show)

Fixed In Version: yum-3.4.3-166.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-31 20:03:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1122 0 None None None 2020-03-31 20:03:49 UTC

Description Peter Portante 2018-11-02 16:18:21 UTC 
Hi Folks, I been receiving yum-cron emails like this:

====

From: (Cron Daemon) <root.com>
Date: Fri, Nov 2, 2018 at 12:05 PM
Subject: [perf-dept-admins] Cron <root@perf48> run-parts /etc/cron.hourly
To: <root.com>


/etc/cron.hourly/0yum-hourly.cron:

Update notice RHBA-2018:3013 (from rhel-7-server-rpms) is broken, or a bad duplicate, skipping.
You should report this problem to the owner of the rhel-7-server-rpms repository.
If you are the owner, consider re-running the same command with --verbose to see the exact data that caused the conflict.

====

But what is the command to re-run with --verbose?  "... consider re-running the same command with --verbose to see the exact data that caused the conflict."
Comment 2 Karel Srot 2018-11-12 07:59:59 UTC 
The message is from yum so there is an assumption that when it was invoked by a user via "yum update" it would be obvious.
The plugin can't alter error messages from yum.
I can imagine that a cmd line equivalent of the yum command used by the plugin could be attached to the email in case of an error. Is that what you mean?
However, it is a yum plugin designed to do updates... so it would be always "yum update ...".
Comment 3 Michal Domonkos 2018-11-29 18:26:03 UTC 
Yeah, this is indeed an error message from yum (more specifically, the routine that handles updateinfo data) which has been added with the assumption it would appear during interactive use ("yum updateinfo list" for example).

I agree we could improve the message to instead say something like "... consider running "yum updateinfo --verbose" to see more details".
Comment 4 Michal Domonkos 2019-09-09 09:08:41 UTC 
Fixed upstream:
https://github.com/rpm-software-management/yum/pull/103

The message
  "If you are the owner, consider re-running the same command with --verbose to see the exact data that caused the conflict."
has been replaced with
  "To help pinpoint the issue, please attach the output of "yum updateinfo --verbose" to the report."
Comment 10 errata-xmlrpc 2020-03-31 20:03:32 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.