[
https://issues.apache.org/jira/browse/AMBARI-19740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15843052#comment-15843052
]
Hadoop QA commented on AMBARI-19740:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12849683/AMBARI-19740-branch-2.5-v1.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/10292//console
This message is automatically generated.
> 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
> Fix For: 2.5.0
>
> 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)
