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

Hudson commented on AMBARI-8667:
--------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #1181 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/1181/])
AMBARI-8667. oozie setting for oozie.authentication.kerberos.principal should 
be fixed in Ambari (alexantonenko) (hiveww: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=836df671abc584f70b94a7728e1ebe12bb5f39c4)
* ambari-web/app/controllers/main/admin/security/add/step2.js
* ambari-web/test/controllers/main/admin/security/add/step2_test.js


> oozie setting for oozie.authentication.kerberos.principal should be fixed in 
> Ambari
> -----------------------------------------------------------------------------------
>
>                 Key: AMBARI-8667
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8667
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>            Priority: Blocker
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8667.patch
>
>
> As of now ambari sets for a specific host. This can lead to issues if oozie 
> is trying to talk to hdfs on another machine.
> {code}
>     <property>
>       <name>oozie.authentication.kerberos.principal</name>
>       
> <value>HTTP/[email protected]</value>
>     </property>
> {code}
> It should be set to:
> {code}
>     <property>
>       <name>oozie.authentication.kerberos.principal</name>
>       <value>HTTP/[email protected]</value>
>     </property>
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to