Bug 1753970

Summary:	/var/log/dnf.rpm.log contains duplicate entries
Product:	Red Hat Enterprise Linux 8	Reporter:	Jan Blazek <jblazek>
Component:	dnf	Assignee:	Jaroslav Mracek <jmracek>
Status:	CLOSED ERRATA	QA Contact:	Luca Berton <lberton>
Severity:	unspecified	Docs Contact:
Priority:	low
Version:	8.0	CC:	adam.winberg, james.antill, lberton, pkratoch
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	dnf-4.2.11-1.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-28 16:48:13 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:

Description Jan Blazek 2019-09-20 11:49:46 UTC

Description of problem:
/var/log/dnf.rpm.log contains duplicate entries for single operations done by dnf.

2019-09-20T11:42:08Z INFO --- logging initialized ---
2019-09-20T11:42:09Z SUBDEBUG Installed: dummypkg-1-1.noarch
2019-09-20T11:42:09Z SUBDEBUG Installed: dummypkg-1-1.noarch
2019-09-20T11:42:10Z INFO --- logging initialized ---
2019-09-20T11:42:10Z SUBDEBUG Erase: dummypkg-1-1.noarch
2019-09-20T11:42:10Z SUBDEBUG Erase: dummypkg-1-1.noarch

Version-Release number of selected component (if applicable):
dnf-4.2.7-6.el8.noarch
libdnf-0.35.1-8.el8.x86_64

How reproducible:
always

Steps to Reproduce:
# yum -y install dummypkg
# yum -y remove dummypkg
check the last entries in /var/log/dnf.rpm.log

Actual results:
Every SUBDEBUG message is present twice.

Expected results:
Every SUBDEBUG should be present just once.

Additional info:
This is a follow-up of bug 1695720.

Comment 1 Pavla Kratochvilova 2019-09-23 11:36:10 UTC

Fixed in upstream, PR: https://github.com/rpm-software-management/dnf/pull/1463
Tests in ci-dnf-stack: https://github.com/rpm-software-management/ci-dnf-stack/pull/595

Comment 7 errata-xmlrpc 2020-04-28 16:48:13 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:1823