[
https://issues.apache.org/jira/browse/AMBARI-12218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14608782#comment-14608782
]
Hadoop QA commented on AMBARI-12218:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12742862/AMBARI-12218_01.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3319//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3319//console
This message is automatically generated.
> 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
>
> Attachments: AMBARI-12218_01.patch
>
>
> 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)
