[
https://issues.apache.org/jira/browse/AMBARI-12289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14615093#comment-14615093
]
Hudson commented on AMBARI-12289:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #3056 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3056/])
AMBARI-12289. Ambari Upgrade: configs are changing HDFS props from
final.(vbrodetskyi) (vbrodetskyi:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f89f7913192aba0a6ef1820c380640ef9af2d494)
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java
> Ambari Upgrade: configs are changing HDFS props from final
> ----------------------------------------------------------
>
> Key: AMBARI-12289
> URL: https://issues.apache.org/jira/browse/AMBARI-12289
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Vitaly Brodetskyi
> Assignee: Vitaly Brodetskyi
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-12289.patch
>
>
> 1) Ambari 1.7 + HDP 2.1
> 2) Upgrade to Ambari 2.1, didn't touch stack
> 3) The following configuration changes should not have been changed. They
> seem unnecessary and we need to avoid making config changes if possible.
> dfs.namenode.http-address, dfs.support.append and fs.defaultFS values were
> not changed, just switched from final to not final.
> We should not be reverting the final unless we really need to.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
