You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Vitaly Brodetskyi (JIRA)" <ji...@apache.org> on 2014/03/03 17:17:23 UTC
[jira] [Updated] (AMBARI-4918) Entering valid directory but not a
java home isn't validated
[ https://issues.apache.org/jira/browse/AMBARI-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vitaly Brodetskyi updated AMBARI-4918:
--------------------------------------
Fix Version/s: 1.5.0
> Entering valid directory but not a java home isn't validated
> ------------------------------------------------------------
>
> Key: AMBARI-4918
> URL: https://issues.apache.org/jira/browse/AMBARI-4918
> Project: Ambari
> Issue Type: Task
> Components: agent
> Affects Versions: 1.5.0
> Reporter: Vitaly Brodetskyi
> Assignee: Vitaly Brodetskyi
> Priority: Critical
> Fix For: 1.5.0
>
>
> During setup, if I choose option (3) for a custom JDK, if I put in a valid directory, but it's not a JDK, it validates.
> Seems like it's only checking that you provided a directory that exists, not that it is a java home.
> {code}
> Do you want to change Oracle JDK [y/n] (n)? y
> [1] - Oracle JDK 1.7
> [2] - Oracle JDK 1.6
> [3] - Custom JDK
> ==============================================================================
> Enter choice (1): 3
> WARNING: JDK must be installed on all hosts and JAVA_HOME must be valid on all hosts.
> WARNING: JCE Policy files are required for configuring Kerberos security. If you plan to use Kerberos,please make sure JCE Unlimited Strength Jurisdiction Policy Files are valid on all hosts.
> Path to JAVA_HOME: /usr
> Validating JDK on Ambari Server...done.
> Completing setup...
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)