[
https://issues.apache.org/jira/browse/AMBARI-12218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-12218:
----------------------------------
Summary: Host check for JDK does not fail when custom JDK is not found
(was: Host check for JDK does fail when custom JDK is not found after changing
JDK option and ambari server setup)
> Host check for JDK does not fail when custom JDK is not found
> -------------------------------------------------------------
>
> Key: AMBARI-12218
> URL: https://issues.apache.org/jira/browse/AMBARI-12218
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Priority: Critical
> Fix For: 2.1.0
>
>
> The host check for JDK does not fail when needed if the JDK is changed to
> manual when running {{ambari-server setup}} the 2nd time.
> If the JDK is to be manually installed and one or more hosts do not have one
> installed (or it cannot be found during the host check), the JDK host check
> should fail. However if {{ambari-server setup}} is run multiple times where
> the first time an automated JDK installation is chosen then the manual option
> is chosen, the {{jdk.name}} property remains set, _confusing_ the host check
> process and thus not failing the check.
> *Steps to reproduce*
> # Install ambari-server
> # install custom JDK on ambari host, only - do not install the JDK anywhere
> else
> # Execute {{ambari-server setup -s}}
> # Execute {{ambari-server setup}}
> # Choose to change the Oracle JDK
> # Select option #3 (Custom JDK)
> # Enter a valid path to a JDK
> # Complete setup
> # Start Ambari
> # Start to create a cluster
> # Enter hosts
> # After the host check, look at the warnings and see that *no error* exists
> for hosts where a JDK was not found
> *Solution*
> Ensure that {{jdk.name}} and {{jce.name}} are not set in the
> ambari.properties file when the custom JDK option is specified.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
