[
https://issues.apache.org/jira/browse/AMBARI-11590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14568755#comment-14568755
]
Hadoop QA commented on AMBARI-11590:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12736718/AMBARI-11590_01.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:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/2975//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/2975//console
This message is automatically generated.
> Kerberos: provide option to set test account name
> -------------------------------------------------
>
> Key: AMBARI-11590
> URL: https://issues.apache.org/jira/browse/AMBARI-11590
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Priority: Critical
> Labels: kerberos
> Fix For: 2.1.0
>
> Attachments: AMBARI-11590_01.patch
>
>
> In many situations with large-scale Active Directory deployments, the
> krb5.conf is managed outside of Ambari. This krb5.conf file is configured
> with all of the DC's in the AD domain, and the outbound requests to the KDC
> from clients are load balanced across those servers. In many scenarios the
> user replication latency causes issues with users not found during the test
> process. Due to the fact that we generate a new user every time we test,
> this can get users to a circular situation in which they can never leave this
> state because of multi-KDC's in their krb5.conf and delay associated with
> replication.
> 1) Expose the option to set the test kerberos client principal name (under
> Advanced kerberos-env)
> 2) Default the value to something unique, but less than 20 characters {code}
> ${cluster_name}-${short_date}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
