[jira] [Commented] (AMBARI-15791) Blueprint based installations should automatically add dfs.internal.nameservices during cluster creation

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-15791:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12797878/AMBARI-15791.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 8 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in ambari-server:

                  org.apache.ambari.server.state.UpgradeHelperTest

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/6330//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6330//console

This message is automatically generated.

> 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: Sumit Mohanty
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15791.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)