[
https://issues.apache.org/jira/browse/AMBARI-8175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin D Jetly updated AMBARI-8175:
-----------------------------------
Description:
# 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
was:
# 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
> 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)
