Bug 1328488 - the engine fails with oracle java8
Summary: the engine fails with oracle java8
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Setup.Core
Version: 3.6.5.1
Hardware: Unspecified
OS: Unspecified
medium
low vote
Target Milestone: ---
: ---
Assignee: Lev Veyde
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-19 13:43 UTC by Fabrice Bacchella
Modified: 2017-06-09 11:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-09 11:27:20 UTC
oVirt Team: Integration
sbonazzo: ovirt-future?


Attachments (Terms of Use)

Description Fabrice Bacchella 2016-04-19 13:43:07 UTC
/usr/share/ovirt-engine/bin/java-home is used to check if the provided OVIRT_ENGINE_JAVA_HOME is good, but in it's check there is :
version="$("${dir}/bin/java" -version 2>&1 | sed \
                                        -e 's/^openjdk version "1\.8\.0.*/VERSION_OK/' \
                                        -e 's/^java version "1\.7\.0.*/VERSION_OK/' \
                                        -e 's/^OpenJDK .*(.*).*/VENDOR_OK/' \
                                )"

So it fails on Oracle Java 8. Is there any good reason for that ?

Comment 1 Fabrice Bacchella 2016-04-19 13:49:11 UTC
Some people might want to try this JVM, its hotspot compiling is supposed to be faster that on openjdk.

Comment 2 Sandro Bonazzola 2016-04-27 12:34:48 UTC
Please note Oracle JVM is not the JVM we tested ovirt-engine on and is not officially supported.

We'll have a look to fix above issue but we can't ensure ovirt-engine will work properly there.

Comment 3 Red Hat Bugzilla Rules Engine 2016-04-27 12:34:51 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 4 Red Hat Bugzilla Rules Engine 2016-04-27 12:36:02 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 5 Sandro Bonazzola 2016-05-02 09:58:59 UTC
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.

Comment 6 Yaniv Lavi 2016-05-23 13:15:50 UTC
oVirt 4.0 beta has been released, moving to RC milestone.

Comment 7 Yaniv Lavi 2016-05-23 13:19:40 UTC
oVirt 4.0 beta has been released, moving to RC milestone.


Note You need to log in before you can comment on or make changes to this bug.