Rebase on upstream 12.0.0.CR1 request, see upstream announcement on http://lists.jboss.org/pipermail/wildfly-dev/2018-February/006384.html
Final has been released: http://wildfly.org/news/2018/02/28/WildFly12-Final-Released/
ping - pnovotny, please check if automation will need update
(In reply to Lukas Svaty from comment #2) > ping - pnovotny, please check if automation will need update No changes in our testing infrastructure are expected.
Retargeting to WildFly 13, which is working much more compatible with engine than WF12.
Verified that ovirt-engine service successfully starts after upgrade from WildFly-11 to WildFly-13. The verification process was: 1) Create CentOS VM 2) Install ovirt-engine 4.2.4 3) engine-setup 4) verify RPM version of ovirt-engine-wildfly, ovirt-engine-wildfly-overlay is 11 5) verify that ovirt-engine service starts successfully 6) Upgrade to snapshot (version 4.2.5) 7) engine-setup 8) verify RPM version of ovirt-engine-wildfly, ovirt-engine-wildfly-overlay is 13 9) verify that ovirt-engine service starts successfully
This bugzilla is included in oVirt 4.2.5 release, published on July 30th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.5 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.