[
https://issues.apache.org/jira/browse/AMBARI-15791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15247062#comment-15247062
]
Hudson commented on AMBARI-15791:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #4680 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4680/])
AMBARI-15791 Blueprint based installations should automatically add (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c623e42701c233fbd04f761b23129555c1f47945])
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java
> Blueprint based installations should automatically add
> dfs.internal.nameservices during cluster creation
> --------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-15791
> URL: https://issues.apache.org/jira/browse/AMBARI-15791
> Project: Ambari
> Issue Type: Bug
> Components: blueprints
> Affects Versions: 2.2.2
> Reporter: Sumit Mohanty
> Assignee: Dmytro Sen
> Fix For: 2.4.0
>
> Attachments: AMBARI-15791-trunk_1.patch
>
>
> Blueprint config processing engine should automatically populate
> {{dfs.internal.nameservices}} when it is deploying HA clusters. The
> work-around till then is to explicitly add the property when submitting the
> blueprint.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
