ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-8175) Security wizard: Cluster deployed with customized user fails to kerberize succesffully
Date Thu, 06 Nov 2014 18:51:34 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-8175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200643#comment-14200643
] 

Hudson commented on AMBARI-8175:
--------------------------------

SUCCESS: Integrated in Ambari-branch-1.7.0 #335 (See [https://builds.apache.org/job/Ambari-branch-1.7.0/335/])
AMBARI-8175. Security wizard: Cluster deployed with customized user fails to kerberize succesffully.
(jaimin) (jaimin: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a7bc7350d49fef867419af3ac794619f3d1c05c2)
* ambari-web/app/controllers/main/admin/security.js
* ambari-web/app/controllers/global/cluster_controller.js


> 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)

Mime
View raw message