[HDP] java64_home not pointing at default-installed JDK for plugin
At this time HDP's java64_home property defaults to /opt/jdk1.6.0_31.
However, the now-default openjdk element installs to /usr/lib/jvm/java-openjdk.
If nodes are connected to the internet at cluster spinup time, this does not
cause an overt error, but querying for JDK location will return error code 2,
resulting in no -j argument being passed to 'ambari-server setup -s', which in
turn will result in a download of Oracle's JDK and successful installation. In
the case that the nodes cannot connect to the internet (which should be a
success case with a pre-installed VM image,) cluster creation fails at this
stage.
This patch updates java64_home to the default JAVA_HOME from the openjdk
element.
Reviewed: https:/ /review. openstack. org/181410 /git.openstack. org/cgit/ openstack/ sahara/ commit/ ?id=23cb825c0d0 b28d043edbef892 4dd10fb7a63a67
Committed: https:/
Submitter: Jenkins
Branch: master
commit 23cb825c0d0b28d 043edbef8924dd1 0fb7a63a67
Author: Ethan Gafford <email address hidden>
Date: Fri May 8 10:30:30 2015 -0400
[HDP] java64_home not pointing at default-installed JDK for plugin
At this time HDP's java64_home property defaults to /opt/jdk1.6.0_31. jvm/java- openjdk.
However, the now-default openjdk element installs to /usr/lib/
If nodes are connected to the internet at cluster spinup time, this does not
cause an overt error, but querying for JDK location will return error code 2,
resulting in no -j argument being passed to 'ambari-server setup -s', which in
turn will result in a download of Oracle's JDK and successful installation. In
the case that the nodes cannot connect to the internet (which should be a
success case with a pre-installed VM image,) cluster creation fails at this
stage.
This patch updates java64_home to the default JAVA_HOME from the openjdk
element.
Change-Id: I1d53db67341626 190e7240f0ae416 5f91d364a2c
Closes-bug: 1453165