Bug 1305482

Summary:	JAVA path expansion
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Pavol Brilla <pbrilla>
Component:	ovirt-engine-sdk-java	Assignee:	Juan Hernández <juan.hernandez>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavol Brilla <pbrilla>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.6.0	CC:	gklein, juan.hernandez, lsurette, mgoldboi, oourfali, pbrilla, yeylon, ykaul
Target Milestone:	ovirt-3.6.3
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	rhevm-sdk-java-3.6.2.0-2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1305871 (view as bug list)		Environment:
Last Closed:	2016-02-17 07:33:05 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pavol Brilla 2016-02-08 11:46:47 UTC

Description of problem:

During erratum run I received:
/usr/src/redhat/BUILD/ovirt-engine-sdk-java-3.6.2.0/generator/regenerate.xml:22: Execute failed: java.io.IOException: Cannot run program "xjc": error=2, No such file or directory


Version-Release number of selected component (if applicable):
rhevm-sdk-java-3.6.2.0-1.el6ev.src.rpm

How reproducible:
100%

Steps to Reproduce:
1.  run ET for rhevm-sdk-java

Actual results:


Expected results:
xjc should be found

Comment 1 Juan Hernández 2016-02-08 11:50:24 UTC

This happens because we assume that the directory /usr/lib/jvm/java-1.8.0-openjdk always exists. But that isn't true, because this is created by the "alternatives" tool, and may not exist in some situations. To avoid this issue we can instead calculate JAVA_HOME like this:

JAVA_HOME=$(dirname $(rpm -ql java-1.8.0-openjdk-devel | grep '/bin$'))

Comment 2 Juan Hernández 2016-02-08 11:51:56 UTC

Pavol, do we need this fixed in order to pass TPS tests, or is there any workaround?

Comment 3 Pavol Brilla 2016-02-09 12:52:08 UTC

Juan, should be fixed, TPS is here to check that we don't need any workarounds

Comment 5 Oved Ourfali 2016-02-11 13:34:59 UTC

Juan - should this be on_qa?

Comment 6 Juan Hernández 2016-02-11 13:40:30 UTC

Yes, it should.

Comment 7 Gil Klein 2016-02-17 07:33:05 UTC

This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA