ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vitaly Brodetskyi (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-14831) Upgrading ambari-server from 2.0.1 to 2.2.0 sets incorrect value for 'storm.zookeeper.superACL'
Date Thu, 28 Jan 2016 15:58:39 GMT
Vitaly Brodetskyi created AMBARI-14831:
------------------------------------------

             Summary: Upgrading ambari-server from 2.0.1 to 2.2.0 sets incorrect value for
'storm.zookeeper.superACL'
                 Key: AMBARI-14831
                 URL: https://issues.apache.org/jira/browse/AMBARI-14831
             Project: Ambari
          Issue Type: Bug
          Components: ambari-upgrade
    Affects Versions: 2.2.0
            Reporter: Vitaly Brodetskyi
            Assignee: Vitaly Brodetskyi
            Priority: Critical
             Fix For: 2.2.2


The problem turns out to be that {{ambari-server upgrade}} from 2.0.1 to 2.2.0 sets the value
of config as ([code|https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=blob;f=ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog210.java;h=7940e02cc627db8e56b91d0aef59336f26c35b78;hb=HEAD#l1651]):

{code}
storm.zookeeper.superACL: "sasl:{{storm_base_jaas_principal}}",
{code}

However STORM scripts expect the config value to be *storm_bare_jaas_principal* ([code|https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=blob;f=ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/kerberos.json;h=5c2133c4c31545ce825208c662086c1d41b7a355;hb=HEAD#l41]).
Because of this, the value comes out as empty. (screenshot attached)



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

Mime
View raw message