Bug 1475459

Summary:	[RFE] Use Wildfly 11 for oVirt engine 4.2
Product:	[oVirt] ovirt-engine	Reporter:	Martin Perina <mperina>
Component:	Packaging.rpm	Assignee:	Martin Perina <mperina>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavol Brilla <pbrilla>
Severity:	high	Docs Contact:
Priority:	high
Version:	---	CC:	bugs, pbrilla
Target Milestone:	ovirt-4.2.0	Keywords:	FutureFeature
Target Release:	4.2.0	Flags:	rule-engine: ovirt-4.2? pstehlik: testing_plan_complete- mperina: planning_ack? mperina: devel_ack+ pstehlik: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-20 10:59:09 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:	1475455
Bug Blocks:	1406751

Description Martin Perina 2017-07-26 18:02:53 UTC

Description of problem:

Use Wildfly 11 for oVirt engine 4.2

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Martin Perina 2017-10-26 10:54:32 UTC

Moving to MODIFIED as WildFly 11.0.0.Final is available using ovirt-engine-wildfly-11.0.0-1.el7 package

Comment 2 Pavol Brilla 2017-11-15 08:41:40 UTC

# yum info ovirt-engine-wildfly
Repository centos-opstools-release is listed more than once in the configuration
Installed Packages
Name        : ovirt-engine-wildfly
Arch        : x86_64
Version     : 11.0.0
Release     : 1.el7.centos
Size        : 178 M
Repo        : installed
From repo   : ovirt-4.2-pre
Summary     : WildFly Application Server for oVirt Engine
URL         : http://jbossas.jboss.org
License     : ASL 2.0
Description : WildFly Application Server for oVirt Engine.

Comment 3 Sandro Bonazzola 2017-12-20 10:59:09 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

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