Bug 1645618

Summary:	yum-cron message directs the user to use --verbose but does not offer the command to use it on
Product:	Red Hat Enterprise Linux 7	Reporter:	Peter Portante <pportant>
Component:	yum	Assignee:	Packaging Maintenance Team <packaging-team-maint>
Status:	CLOSED ERRATA	QA Contact:	Jan Blazek <jblazek>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	7.5	CC:	james.antill, ksrot, kwalker, mdomonko, pportant
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	yum-3.4.3-166.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-31 20:03:32 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1630909

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