[
https://issues.apache.org/jira/browse/AMBARI-12284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14660611#comment-14660611
]
Hadoop QA commented on AMBARI-12284:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12749079/AMBARI-12284_trunk_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/3540//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3540//console
This message is automatically generated.
> Ambari omits the line to enable kerberos on the Spark History Service
> ---------------------------------------------------------------------
>
> Key: AMBARI-12284
> URL: https://issues.apache.org/jira/browse/AMBARI-12284
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Steve Loughran
> Assignee: Robert Levas
> Fix For: 2.2.0
>
> Attachments: AMBARI-12284_branch-2.1_01.patch,
> AMBARI-12284_trunk_01.patch
>
>
> Ambari omits the line to enable kerberos on the Spark History Service
> When Ambari sets up a secure spark cluster, it doesn't set
> This will still fail tests unless the line
> spark.history.kerberos.enabled true
> is added to spark-defaults.conf
> without this the Spark History Service will not log in with the keytab, and
> so not set up a long-lived secure connection to a Yarn History Server with
> encryption on.
> This isn't immediately visible (and hard to sport in the tests), because if
> the user spark has logged in with kinit, the TGT is picked up and used —which
> works until the ticket expires.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
