Bug 1545596

Summary: engine-setup should configure versionlock yum plugin to follow Obsoletes
Product: [oVirt] ovirt-engine Reporter: Yedidyah Bar David <didi>
Component: Setup.CoreAssignee: Yedidyah Bar David <didi>
Status: CLOSED CURRENTRELEASE QA Contact: Lucie Leistnerova <lleistne>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: bugs, didi, jbelka, lsurette, rbalakri, Rhev-m-bugs, sbonazzo, srevivo, ykaul, ylavi
Target Milestone: ovirt-4.2.2Keywords: ZStream
Target Release: ---Flags: rule-engine: ovirt-4.2+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1543526
: 1545598 (view as bug list) Environment:
Last Closed: 2018-03-29 11:12:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1543526    
Bug Blocks: 1545598    

Description Yedidyah Bar David 2018-02-15 10:34:22 UTC 
engine-setup should configure yum's versionlock plugin to follow Obsoletes, so that if/when we rename locked packages, 'yum update' won't install the new ones, but let engine-setup do that.
Comment 2 Lucie Leistnerova 2018-02-22 12:52:14 UTC 
after running engine-setup follow_obsoletes=1 is in /etc/yum/pluginconf.d/versionlock.conf

verified in ovirt-engine-setup-4.2.2.1-0.1.el7.noarch
Comment 3 Sandro Bonazzola 2018-03-29 11:12:07 UTC 
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.