Bug 1475455

Summary:	Package Wildfly 11 as ovirt-engine-wildfly
Product:	[oVirt] ovirt-distribution	Reporter:	Martin Perina <mperina>
Component:	ovirt-engine-wildfly10	Assignee:	Martin Perina <mperina>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavol Brilla <pbrilla>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2.0	CC:	bugs, lsvaty, mgoldboi, mperina, pbrilla, sbonazzo
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+ lsvaty: testing_ack+
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-20 11:43:16 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:
Bug Blocks:	1475459

Description Martin Perina 2017-07-26 18:00:26 UTC

Description of problem:

Create a package providing Wildfly 11 for Fedora and CentOS for oVirt 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-08-17 08:43:00 UTC

Leaving on POST as currently we use WildFly 11.0.0.Beta1, but we want to upgrade to GA as soon as it's available.

Comment 2 Yaniv Kaul 2017-10-26 11:37:46 UTC

(In reply to Martin Perina from comment #1)
> Leaving on POST as currently we use WildFly 11.0.0.Beta1, but we want to
> upgrade to GA as soon as it's available.

Can we move this BZ to MODIFIED now?

Comment 3 Martin Perina 2017-10-26 11:51:45 UTC

Sorry, I moved the RFE and forgot about this one :-(

Comment 4 Pavol Brilla 2017-11-15 09:04:22 UTC

Package available in ovirt resources:
http://resources.ovirt.org/pub/ovirt-4.2-pre/rpm/el7Server/x86_64/ovirt-engine-wildfly-11.0.0-1.el7.centos.x86_64.rpm

Comment 5 Sandro Bonazzola 2017-12-20 11:43:16 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.