[ovirt-devel] Engine on Fedora 21

[Roy Golan]

On 02/03/2015 12:28 AM, Adam Litke wrote:
> On 02/02/15 15:41 -0500, Greg Sheremeta wrote:
>>
>>
>> ----- Original Message -----
>>> From: "Adam Litke" <alitke at redhat.com>
>>> To: "Juan Hernández" <jhernand at redhat.com>
>>> Cc: devel at ovirt.org
>>> Sent: Monday, February 2, 2015 2:26:29 PM
>>> Subject: Re: [ovirt-devel] Engine on Fedora 21
>>>
>>> On 02/02/15 13:55 +0100, Juan Hernández wrote:
>>> >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 at redhat.com>
>>> >>>>> To: devel at 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.
>>>
>>> Thanks for the suggestions everyone.  I ended up installing
>>> openJDK-1.7 alongside the stock 1.8 and it's working again for me.
>>
>> via yum or did you just download it?
>
> Both :)  I had to use yumdownloader to grab the rpms from the f20 repo
> and then install them using rpm --nodeps (since the 1.8 rpms from f21
> have an Obseletes: openjdk-1.7).
>
>>
>> Perhaps depending on your answer, can't this fulfill the F21 support
>> feature?
>>
>>> I'll try to give those other JBoss versions a try soon though.
>>>
>>> -- 
>>> Adam Litke
>>> _______________________________________________
>>> Devel mailing list
>>> Devel at ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>
>

I work with F21 currently by installing Oracle jdk 7 rpm (download from 
oracle site)

then use 2 env variables to make ovirt work with it:

export OVIRT_ENGINE_JAVA_HOME=/usr/java/jdk1.7.0.75
export OVIRT_ENGINE_JAVA_HOME_FORCE=1

and use the regular jboss-as-7.1.1 from tar.gz

the only problem found currently is with creating the engin.p12 key 
during setup [1]

the workaround is to copy any other working engin.p12 from previous 
setup you had

the engine.p12 file is under etc/pki/ovirt-engine/keys/engine.p12

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1193776