Bug 1323127
| Summary: | /usr/share/ovirt-engine/bin/java-home should take into account reports and then exclude java 1.8 | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Jiri Belka <jbelka> |
| Component: | Setup.Core | Assignee: | Yedidyah Bar David <didi> |
| Status: | CLOSED DUPLICATE | QA Contact: | Pavel Stehlik <pstehlik> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.6.5 | CC: | bugs |
| Target Milestone: | ovirt-3.6.5 | Flags: | sbonazzo:
ovirt-3.6.z?
rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack? |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-04-10 09:11:58 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
this is especially more serious in 4.0 where java-home script has hardcoded 1.8.x java only! https://bugzilla.redhat.com/show_bug.cgi?id=1303132 IMO this is not real solution but manual workaround which would probably break on every other java implementation/version installation as i bet it would change default system java :) Didi isn't this solved by your recent patches? (In reply to Sandro Bonazzola from comment #3) > Didi isn't this solved by your recent patches? Should be. *** This bug has been marked as a duplicate of bug 1303132 *** |
Description of problem: reports do not work with java 1.8.x, unsupported by jaspersoft, but /usr/share/ovirt-engine/bin/java-home acceptes java 1.8.x blindly - if available on system and set as default by "alternatives". this causes engine-setup to fail if reports are installed as 1.8.x is not supported. imo /usr/share/ovirt-engine/bin/java-home should take into account installed reports and then exclude 1.8.x or there should be separate check for reports setup to "always" use 1.7.x. [ INFO ] Exporting data out of Jasper [ ERROR ] Failed to execute stage 'Misc configuration': Command './js-export.sh' failed to execute [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20160331134938-z7s8ug.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20160331140054-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed # /usr/share/ovirt-engine/bin/java-home /usr/lib/jvm/jre ]# /usr/lib/jvm/jre/bin/java -version openjdk version "1.8.0_77" OpenJDK Runtime Environment (build 1.8.0_77-b03) OpenJDK 64-Bit Server VM (build 25.77-b03, mixed mode) update-alternatives --config java and selecting 1.7.x solves the issue as default java would be 1.7.x which satisfies both engine jboss and jasper reports. Version-Release number of selected component (if applicable): 3.6.5 How reproducible: 100% Steps to Reproduce: 1. install openjdk 1.8.x and openjdk 1.7.x 2. ensure java -version returns 1.8.x 3. engine-setup with reports installed (i had reports for long time, so i'm not sure if this would be "visible" on clean env) Actual results: 1.8.x java causes engine-setup failure as jasper reports do not support 1.8.x java Expected results: we should have a workaround for it when java -version returns 1.8.x as default system java and force 1.7.x for reports _EVEN_ during engine-setup (as engine-setup calls jasper scripts which would load default java). Additional info: