ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [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
Date Mon, 21 Aug 2017 21:43:00 GMT


Hudson commented on AMBARI-21769:

FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #39 (See [])
AMBARI-21769. zeppelin principal and livy.superusers property do not (rlevas: [])
* (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK/kerberos.json
* (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/
* (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/
* (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/
* (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/
* (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/SPARK/kerberos.json
* (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/kerberos.json
* (edit) ambari-server/src/test/python/stacks/2.6/common/
* (edit) ambari-server/src/test/python/stacks/2.5/common/
* (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/

> 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:
>             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,
> 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

View raw message