[jira] [Commented] (AMBARI-13099) Host group level config changes are not picked up with Blueprint provisioning

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

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

Hadoop QA commented on AMBARI-13099:
------------------------------------

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

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

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {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:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

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

This message is automatically generated.

> Host group level config changes are not picked up with Blueprint provisioning
> -----------------------------------------------------------------------------
>
>                 Key: AMBARI-13099
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13099
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.1
>            Reporter: Olivér Szabó
>            Assignee: Olivér Szabó
>            Priority: Blocker
>             Fix For: 2.1.2
>
>         Attachments: AMBARI-13099.patch
>
>
> Installing a cluster with a blueprint that contains host group level configurations are not picked up during install time. Ambari UI complains to restart few services after installation which doesn't make sense.
> In the provided BP there are host group level config like: 
> {
> "hdfs-site" :
> { "dfs.datanode.data.dir" : "/hadoopfs/fs1/hdfs/datanode,/hadoopfs/fs2/hdfs/datanode" }
> },
> {
> "yarn-site" :
> { "yarn.nodemanager.local-dirs" : "/hadoopfs/fs1/yarn/nodemanager,/hadoopfs/fs2/yarn/nodemanager", "yarn.nodemanager.log-dirs" : "/hadoopfs/fs1/yarn/nodemanager/log,/hadoopfs/fs2/yarn/nodemanager/log" }
> }
> and those directories are not in use, but the default ones.



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