[
https://issues.apache.org/jira/browse/AMBARI-10356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395252#comment-14395252
]
Hadoop QA commented on AMBARI-10356:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12709337/AMBARI-10356.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/2247//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/2247//console
This message is automatically generated.
> Ambari Upgrade from 1.6.1 to 1.7.0 fails when analyzing global config groups
> with certain data
> ----------------------------------------------------------------------------------------------
>
> Key: AMBARI-10356
> URL: https://issues.apache.org/jira/browse/AMBARI-10356
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 1.7.0
> Reporter: Alejandro Fernandez
> Fix For: 2.1.0
>
> Attachments: AMBARI-10356.patch
>
>
> Some values in the config_data column of table clusterconfig prevent
> UpgradeCatalog170 from passing.
> E.g.,
> {code}
> {"zk_data_dir":"/hadoop/zookeeper"}
> {code}
> because the key is not a type that is recognized in the known config-types.
> I verified that the patch works, and was able to upgrade Ambari from 1.6.1 ->
> 1.7.0 -> 2.0.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
