ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Renjith Kamath (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-19740) Ambari upgrade to Ambari 2.5 causes start DB check failure on Zeppelin configs
Date Fri, 27 Jan 2017 12:41:24 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-19740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Renjith Kamath updated AMBARI-19740:
------------------------------------
    Status: Patch Available  (was: Open)

> Ambari upgrade to Ambari 2.5 causes start DB check failure on Zeppelin configs
> ------------------------------------------------------------------------------
>
>                 Key: AMBARI-19740
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19740
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Renjith Kamath
>            Assignee: Renjith Kamath
>         Attachments: AMBARI-19740-branch-2.5-v1.patch
>
>
> Ambari upgrade to Ambari 2.5 causes start DB check failure on Zeppelin configs:
> {noformat}
> 017-01-11 15:50:16,078  INFO - Comparing required service configs from stack with mapped
service configs from db
> 2017-01-11 15:50:16,084 ERROR - Required config(s): zeppelin-log4j-properties,zeppelin-shiro-ini
is(are) not available for service ZEPPELIN with service config version 3 in cluster c1
> 2017-01-11 15:50:16,084  INFO - Getting services which has mapped configs which are not
selected in clusterconfigmapping
> {noformat}
> HDP version 2.5 was not upgraded. 
> *Steps to reproduce*
> # Install Ambari 2.4.2
> # Create cluster using HDP 2.5 - including Zeppelin
> # Enable Kerberos (probably not necessary)
> # Upgrade Ambari to 2.5.0
> # Attempt to start Ambari
> # See error message in {{/var/log/ambari-server/ambari-server-check-database.log}}



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

Mime
View raw message