You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2016/05/25 13:27:13 UTC

[jira] [Commented] (AMBARI-16822) Hostname substitutions for Namenode HA Initial State properties does not work

    [ https://issues.apache.org/jira/browse/AMBARI-16822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300030#comment-15300030 ] 

Hudson commented on AMBARI-16822:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #4920 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4920/])
AMBARI-16822. Hostname substitutions for Namenode HA Initial State (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7fa34c7189dd14c410df162d9579934002b9ba84])
* ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java


> Hostname substitutions for Namenode HA Initial State properties does not work
> -----------------------------------------------------------------------------
>
>                 Key: AMBARI-16822
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16822
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.0
>            Reporter: Balázs Bence Sári
>            Assignee: Balázs Bence Sári
>             Fix For: 2.4.0
>
>         Attachments: diff2.patch
>
>
> {code}
> {
>       "hadoop-env": {
>         "properties" : {
>           "dfs_ha_initial_namenode_active" : "%HOSTGROUP::master_1%",
>           "dfs_ha_initial_namenode_standby" : "%HOSTGROUP::master_2%"
>       }}
> }
> {code}
> When these properties are included in the blueprint during HA blueprint deployment hostname substitutions do not work. Other properties in the blueprint get substituted correctly. 
> Talked to [~rnettleton] about the issue and he verified that this is an issue in BlueprintConfigurationProcessor



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)