Re: [ovirt-devel] Engine on Fedora 21

On 02/02/2015 07:56 AM, Sandro Bonazzola wrote: > Il 29/01/2015 22:30, Adam Litke ha scritto: >> On 29/01/15 16:18 -0500, Yedidyah Bar David wrote: >>> ----- Original Message ----- >>>> From: "Adam Litke" <alitke(a)redhat.com&gt; >>>> To: devel(a)ovirt.org >>>> Sent: Thursday, January 29, 2015 9:46:27 PM >>>> Subject: [ovirt-devel] Engine on Fedora 21 >>>> >>>> Hi all, >>>> >>>> Today I tried running engine on my Fedora 21 laptop. I tried two >>>> approaches for deploying jboss: using the ovirt-jboss-as package, and >>>> by downloading and unpacking jboss-7.1.1 into /usr/share as I have >>>> done in the past. engine-setup runs without errors but when I try to >>>> start engine the application does not seem to deploy in jboss and >>>> there are no errors reported (engine.log is empty). >>>> >>>> Is there a reasonable expectation that I should be able to get this >>>> working on F21 or am I wasting my time? Does anyone have any ideas >>>> on how I can resolve the startup issues? >>> >>> Which Java version did you try to use it with? >> >> java-1.8.0-openjdk-1.8.0.31-3.b13.fc21.x86_64 >> >>> Did you have a look at [1]? In short: won't be, wait for f22. >> >> Yeah, didn't see much documentation of specific issues and the tracker >> bug looks pretty clean as far as general engine usability goes. >> > > Everything should be installable right now in F21 but jboss-as 7.1 doesn't work with java 1.8. > We'll need to move to wildfly or backport java7 in order to make it working. > Alternatively, if it is for development purposes only, you may want to consider using JBoss EAP 6.x instead of JBoss AS 7.1.1. The root cause of the incompatibility has been fixed there (and in WildFly): https://issues.jboss.org/browse/WFLY-2057 You can get JBoss EAP from here: http://www.jboss.org/products/eap/download Then you can unzip it to your favorite directory and use it during installation of oVirt Engine: # engine-setup --jboss-home=/whatever/jboss-eap-6.3 It should work well with Java 8. If it doesn't work it is good to know, as we will need to fix it eventually.