Bug 1719679

Summary:	Module is marked as installed even if the rpm transaction check failed
Product:	Red Hat Enterprise Linux 8	Reporter:	Marek Blaha <mblaha>
Component:	dnf	Assignee:	Marek Blaha <mblaha>
Status:	CLOSED ERRATA	QA Contact:	Luca Berton <lberton>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.1	CC:	amatej, james.antill, lberton
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.0	Flags:	pm-rhel: mirror+
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:47:49 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 Marek Blaha 2019-06-12 10:37:17 UTC

Description of problem:
When installing of a module profile failed on rpm transaction check, the module stream is still marked as enabled and the profile as installed.

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

How reproducible:
100%

Steps to Reproduce:

Scenario: Profile is not installed after its artifact failed to get installed from ci-dnf-stack module-install-errors.feature

1. install package which file-conflicts with the package from module stream
2. dnf module install module:stream/profile
this fails with Transaction check error

Actual results:
The module:stream/profile is marked as installed and module:stream is enabled

Expected results:
Neither profile is installed, neither stream enabled

Additional info:

Comment 1 Marek Blaha 2019-06-12 11:13:38 UTC

PR: https://github.com/rpm-software-management/dnf/pull/1412

Comment 2 Marek Blaha 2019-06-18 09:35:54 UTC

*** Bug 1680684 has been marked as a duplicate of this bug. ***

Comment 8 errata-xmlrpc 2020-04-28 16:47:49 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