Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1545598

Summary: [downstream clone - 4.1.10] engine-setup should configure versionlock yum plugin to follow Obsoletes
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: ovirt-engineAssignee: Yedidyah Bar David <didi>
Status: CLOSED ERRATA QA Contact: Lucie Leistnerova <lleistne>
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: bugs, didi, jbelka, lsurette, rbalakri, Rhev-m-bugs, sbonazzo, srevivo, ykaul, ylavi
Target Milestone: ovirt-4.1.10Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1545596 Environment:
Last Closed: 2018-03-20 16:37:08 UTC Type: ---
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: 1545596    
Bug Blocks:    

Description rhev-integ 2018-02-15 10:46:23 UTC
+++ This bug is an upstream to downstream clone. The original bug is: +++
+++   bug 1545596 +++
======================================================================

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.

(Originally by didi)

Comment 2 Lucie Leistnerova 2018-02-23 09:27:30 UTC
After running engine-setup follow_obsoletes=1 is in /etc/yum/pluginconf.d/versionlock.conf

verified in ovirt-engine-4.1.10.1-0.1.el7.noarch

Comment 5 errata-xmlrpc 2018-03-20 16:37:08 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2018:0562

Comment 6 Franta Kust 2019-05-16 13:09:20 UTC
BZ<2>Jira Resync