Bug 1283267

Summary: minidnf should not remove leftover packages when doing a rollback
Product: [oVirt] otopi Reporter: Rafael Martins <rmartins>
Component: Plugins.packagersAssignee: Yedidyah Bar David <didi>
Status: CLOSED CURRENTRELEASE QA Contact: Karolína Hajná <khajna>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.4.0CC: bugs, gklein, pstehlik, sbonazzo, ylavi
Target Milestone: ovirt-3.6.3Flags: rule-engine: ovirt-3.6.z+
ylavi: planning_ack+
rule-engine: devel_ack+
pstehlik: testing_ack+
Target Release: 1.4.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-17 07:40:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1306019    

Description Rafael Martins 2015-11-18 14:45:50 UTC
When some otopi consumer asks for a rollback after installing packages using minidnf, it should only remove the packages that were explicitly installed during that transaction.

This is related to the DNF behaviour when removing package requirements. See: http://dnf.readthedocs.org/en/latest/conf_ref.html#clean-requirements-on-remove-label

Comment 1 Red Hat Bugzilla Rules Engine 2015-11-18 15:19:02 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 3 Sandro Bonazzola 2016-02-09 07:01:32 UTC
Moving back to modified, 1.4.1 has not been released.

Comment 4 Gil Klein 2016-02-17 07:40:10 UTC
This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA