sahara/sahara/plugins/hdp/versions/version_2_0_6/resources
Ethan Gafford 23cb825c0d [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.

Change-Id: I1d53db67341626190e7240f0ae4165f91d364a2c
Closes-bug: 1453165
2015-05-08 10:30:30 -04:00
..
ambari-config-resource.json Enable HDFS NameNode High Availability with HDP 2.0.6 plugin 2014-12-12 09:20:00 +01:00
default-cluster.template [HDP] java64_home not pointing at default-installed JDK for plugin 2015-05-08 10:30:30 -04:00
topology.sh Fix bashate errors 2014-10-08 18:21:49 +04:00