[
https://issues.apache.org/jira/browse/AMBARI-15788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15241590#comment-15241590
]
Hudson commented on AMBARI-15788:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #4656 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4656/])
AMBARI-15788 Ambari upgrade should auto-populate (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6d081b19a5637e4f5682daf1dcc27f6b1a5e8b60])
*
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java
> Ambari upgrade should auto-populate dfs.internal.nameservice
> ------------------------------------------------------------
>
> Key: AMBARI-15788
> URL: https://issues.apache.org/jira/browse/AMBARI-15788
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
> Affects Versions: 2.2.2
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Fix For: 2.4.0
>
> Attachments: AMBARI-15788.patch
>
>
> As part of this task, Ambari upgrade code should be modified to automatically
> add {{dfs.internal.nameservices}} based on what value exists in
> {{dfs.nameservices}}. It can be assumed that the value will be valid (not a
> comma separated string) as if its a working cluster managed by Ambari then
> {{dfs.nameservices}} cannot contain multiple nameservices.
> Another upgrade task is to modify the alert definitions to switch to the new
> property.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
