Bug 1545596 - engine-setup should configure versionlock yum plugin to follow Obsoletes
Summary: engine-setup should configure versionlock yum plugin to follow Obsoletes
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Setup.Core
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.2.2
: ---
Assignee: Yedidyah Bar David
QA Contact: Lucie Leistnerova
URL:
Whiteboard:
Depends On: 1543526
Blocks: 1545598
TreeView+ depends on / blocked
 
Reported: 2018-02-15 10:34 UTC by Yedidyah Bar David
Modified: 2019-04-28 13:49 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1543526
: 1545598 (view as bug list)
Environment:
Last Closed: 2018-03-29 11:12:07 UTC
oVirt Team: Integration
Embargoed:
rule-engine: ovirt-4.2+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 87577 0 None None None 2018-02-15 10:34:21 UTC
oVirt gerrit 87667 0 ovirt-engine-4.2 MERGED packaging: setup: Configure yum versionlock plugin to follow obsoletes 2018-02-15 10:58:24 UTC
oVirt gerrit 88018 0 master MERGED packaging: setup: Condition changing versionlock.conf 2018-02-21 09:50:44 UTC
oVirt gerrit 88021 0 ovirt-engine-4.2 MERGED packaging: setup: Condition changing versionlock.conf 2018-02-21 10:37:36 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.