[
https://issues.apache.org/jira/browse/AMBARI-21999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16173354#comment-16173354
]
Hudson commented on AMBARI-21999:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8104 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8104/])
AMBARI-21999 - Always Take Target Read-Only Properties On Stack Upgrade
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=56c3da7846cf2b30e5860cb5bc32d3c9ecb93424])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeHelper.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/StackUpgradeConfigurationMergeTest.java
> Always Take Target Read-Only Properties On Stack Upgrade
> --------------------------------------------------------
>
> Key: AMBARI-21999
> URL: https://issues.apache.org/jira/browse/AMBARI-21999
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.5.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21999.patch
>
>
> STR:
> - Install a stack, such as HDP 2.3
> - Modify the {{cluster-env/stack_features}} structure
> - Upgrade to HDP 2.6
> The auto-merge which happens can't properly merge
> {{cluster-env/stack_features}} since it has deviated from the stock values of
> HDP 2.3. This is dangerous since this is needed for proper operation.
> Because it's defined as a read-only value, we should be able to detect this
> in the auto-merge fro the upgrade and force it to the new stack's default
> value...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
