Bug 1395515

Summary: dnf group install registers group as installed prematurely
Product: [Fedora] Fedora Reporter: Yaakov Selkowitz <yselkowi>
Component: dnfAssignee: rpm-software-management
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 25CC: mluscon, packaging-team-maint, pnemade, rpm-software-management, vmukhame
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-16 07:53:44 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:

Description Yaakov Selkowitz 2016-11-16 04:56:24 UTC 
Description of problem:
dnf registers a group as installed even if the transaction which would have installed it does not complete.

Version-Release number of selected component (if applicable):
dnf-1.1.10-3.fc25

How reproducible:
100%

Steps to Reproduce:
1. Install F25 Beta Workstation.
2. dnf update
3. dnf install @kde-desktop --allowerasing OR dnf groupinstall 'KDE' -allowerasing
4. Press no at the "Is this ok" prompt.

Actual results:
Currently, --allowerasing is required, as without which dnf fails due to something requiring a downgrade of firewalld.  Whether this succeeds far enough to reach the confirmation query, or even when this fails due to the lack of --allowerasing, the group is registered as having been installed even though no packages have been.  A subsequent attempt at the same transaction errors out:

Group "KDE" is already installed, skipping.

Expected results:
The group is not registered as installed at this point (as on F24), and a subsequent attempt will proceed normally.

Additional info:
This is not limited to the KDE group; this has occurred with several other DE groups.
Comment 1 Igor Gnatenko 2016-11-16 07:53:44 UTC 

*** This bug has been marked as a duplicate of bug 1384386 ***