Bug 1395515 - dnf group install registers group as installed prematurely
Summary: dnf group install registers group as installed prematurely
Keywords:
Status: CLOSED DUPLICATE of bug 1384386
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: rpm-software-management
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-16 04:56 UTC by Yaakov Selkowitz
Modified: 2016-11-16 07:53 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-16 07:53:44 UTC
Type: Bug


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.