[
https://issues.apache.org/jira/browse/AMBARI-10356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493243#comment-14493243
]
Hudson commented on AMBARI-10356:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2294 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2294/])
AMBARI-10356. Ambari Upgrade from 1.6.1 to 1.7.0 fails when analyzing global
config groups with certain data (alejandro) (afernandez:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e5e72d80d898569d0583e227e9a694f09a559f67)
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog170.java
> 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
> Assignee: 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)
