[jira] [Commented] (AMBARI-21769) zeppelin principal and livy.superusers property do not match on upgraded cluster from Ambari 2.4.2 -and HDP 2.5.5

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-21769:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12882906/AMBARI-21769_branch-2.5_01.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12034//console

This message is automatically generated.

> zeppelin principal and livy.superusers property do not match on upgraded cluster from Ambari 2.4.2 -and HDP 2.5.5
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-21769
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21769
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.2
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Blocker
>             Fix For: 2.5.2
>
>         Attachments: AMBARI-21769_branch-2.5_01.patch, AMBARI-21769_branch-2.6_01.patch, AMBARI-21769_trunk_01.patch
>
>
> In a cluster where the Spark and/or Spark2 Livy servers and Zeppelin are installed and Kerberos is enabled, it is expected that that {{livy-conf/livy.superusers}} and {{livy2-conf/livy.superusers}} contain the principal name of the Zeppelin user.  However, this value is not always set, depending on the order in which the services were installed, when Kerberos was enabled, and whether an Ambari or stack upgrade was involved.  And if it is set, the value may be incorrect since the Kerberos descriptor assumes the Zeppelin principal is {{zeppelin-<clustername>}}
> The solution is to move the logic to set the {{livy-conf/livy.superusers}} and {{livy2-conf/livy.superusers}} to the stack advisor to the appropriate value can be added as needed.  Also while upgrading to Ambari 2.5.2, the value(s) should be fixed if necessary. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)