[
https://issues.apache.org/jira/browse/AMBARI-10323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392063#comment-14392063
]
Hadoop QA commented on AMBARI-10323:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12708871/AMBARI-10323.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{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:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/2215//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/2215//console
This message is automatically generated.
> Alerts: Hive Metastore And HS2 Process Alerts Do Not Work With Custom Smoke
> User
> --------------------------------------------------------------------------------
>
> Key: AMBARI-10323
> URL: https://issues.apache.org/jira/browse/AMBARI-10323
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-10323.patch
>
>
> Both the Hive Metastore and HS2 alerts do not pickup a custom smoke user when
> running in a Kerberized environment. They both default to {{ambari-qa}}.
> The {{SMOKEUSER_KEY}} is missing from the tuple of keys.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
