[
https://issues.apache.org/jira/browse/AMBARI-8175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199799#comment-14199799
]
Hadoop QA commented on AMBARI-8175:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12679777/AMBARI-8175.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 .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/518//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/518//console
This message is automatically generated.
> Security wizard: Cluster deployed with customized user fails to kerberize
> succesffully
> --------------------------------------------------------------------------------------
>
> Key: AMBARI-8175
> URL: https://issues.apache.org/jira/browse/AMBARI-8175
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 1.7.0
> Reporter: Jaimin D Jetly
> Assignee: Jaimin D Jetly
> Priority: Blocker
> Fix For: 1.7.0
>
> Attachments: AMBARI-8175.patch, AMBARI-8175_branch-1.7.0.patch
>
>
> # JobHistoryServer failed to start after enabling security with a customized
> user name 'mapred1' (CSV file has wrong user name and core-site
> hadoop.security.auth_to_local does not have correct mapping for mapred)
> # With customized user, If browser refresh is done on "Stop Services" command
> of Deploy step then hadoop.security.auth_to_local gets configured with
> default user names for all services and results in either service start
> failure or service heck failure
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
