[
https://issues.apache.org/jira/browse/AMBARI-21582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16102298#comment-16102298
]
Hudson commented on AMBARI-21582:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1748 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1748/])
AMBARI-21582 - Stack Tools and Feature Should be Ignored in Blueprints
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=84317d92c989d17ae9bc179d859cf53a244ce78b])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
> Stack Tools and Feature Should be Ignored in Blueprints
> -------------------------------------------------------
>
> Key: AMBARI-21582
> URL: https://issues.apache.org/jira/browse/AMBARI-21582
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.5.2
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21582.patch
>
>
> AMBARI-21430 introduced the ability for multiple stack tools to exist in
> {{cluster-env}}. In order to remain backward compatible with existing
> blueprints, it was decided that all stack tools and features properties
> specified on a blueprint would be ignored in favor of what was defined on the
> stack.
> There is a bug in the logic which overrides the blueprint properties where
> the wrong map is consulted for a matching key. This causes the properties
> specified in the blueprint to be used instead of those from the stack.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
