Bug 1264435

Summary: ovirt-engine-wildfly should be added to version locking
Product: [oVirt] ovirt-engine Reporter: Sandro Bonazzola <sbonazzo>
Component: Setup.EngineCommonAssignee: Simone Tiraboschi <stirabos>
Status: CLOSED CURRENTRELEASE QA Contact: Gonza <grafuls>
Severity: medium Docs Contact:
Priority: high    
Version: 3.6.0CC: bmcclain, bugs, didi, juan.hernandez, lveyde, rmartins, stirabos
Target Milestone: ovirt-3.6.0-gaKeywords: FutureFeature
Target Release: 3.6.0Flags: rule-engine: ovirt-3.6.0+
bmcclain: planning_ack+
sbonazzo: devel_ack+
pstehlik: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: integration
Fixed In Version: Doc Type: Enhancement
Doc Text:
We're currently using ovirt-engine-wildfly-8.2.0 final in 3.6 and we're already going to test 10 CR1 on master. We don't want that a casual yum update / dnf update may break the running engine. So we need to lock the version of ovirt-engine-wildfly as well and allow the setup to take care of the update.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-04 11:21:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sandro Bonazzola 2015-09-18 13:11:11 UTC
We're currently using ovirt-engine-wildfly-8.2.0 final in 3.6 and we're already going to test 10 CR1 on master.
We don't want that a casual yum update / dnf update may break the running engine.
So we need to lock the version of ovirt-engine-wildfly as well and allow the setup to take care of the update.

Comment 1 Yedidyah Bar David 2015-09-21 13:17:26 UTC
Isn't it enough to Conflict?

Comment 2 Gonza 2015-10-20 14:14:42 UTC
Verified with:
ovirt-engine-3.6.1-0.0.master.20151019163841.gitacec65b.el6.noarch

# cat /etc/yum/pluginconf.d/versionlock.list
ovirt-engine-webadmin-portal-3.6.1-0.0.master.20151019163841.gitacec65b.el6.noarch
ovirt-engine-wildfly-8.2.0-1.el6.x86_64
ovirt-engine-restapi-3.6.1-0.0.master.20151019163841.gitacec65b.el6.noarch
ovirt-engine-dbscripts-3.6.1-0.0.master.20151019163841.gitacec65b.el6.noarch
ovirt-engine-userportal-3.6.1-0.0.master.20151019163841.gitacec65b.el6.noarch
ovirt-engine-3.6.1-0.0.master.20151019163841.gitacec65b.el6.noarch
ovirt-engine-backend-3.6.1-0.0.master.20151019163841.gitacec65b.el6.noarch
ovirt-engine-wildfly-overlay-001-2.el6.noarch
ovirt-engine-tools-3.6.1-0.0.master.20151019163841.gitacec65b.el6.noarch

Comment 3 Sandro Bonazzola 2015-11-04 11:21:59 UTC
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.