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-6496) Ambari fails to start services because it still tries to kinit for hdfs_user when hdfs_principal_name is customized.
Date Tue, 26 Aug 2014 19:13:57 GMT

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

Hudson commented on AMBARI-6496:
--------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #29 (See [https://builds.apache.org/job/Ambari-trunk-Commit/29/])
AMBARI-6496. Additional fix: keberization needs hdfs_principal_name property to be saved in
hadoop-env section of command file, otherwise it fails. (Alejandro Fernandez via swagle) (swagle:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e984e9b844721efd8eef8ddf781c9ff74486d85c)
* ambari-web/app/data/HDP2/secure_properties.js


> Ambari fails to start services because it still tries to kinit for hdfs_user when hdfs_principal_name
is customized.
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-6496
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6496
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.6.1
>            Reporter: Mahadev konar
>            Assignee: Alejandro Fernandez
>             Fix For: 1.7.0
>
>
> Ambari fails to start services because it still tries to kinit for hdfs_user when hdfs_principal_name
is customized.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message