Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 24 Nov 2015 15:58:10 +0000 (UTC)
From: "Aleksandr Kovalenko (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12915832.1448380582000.177193.1448380690970@Atlassian.JIRA>
In-Reply-To: <JIRA.12915832.1448380582000@Atlassian.JIRA>
References: <JIRA.12915832.1448380582000@Atlassian.JIRA>
 <JIRA.12915832.1448380582713@arcas>
Subject: [jira] [Updated] (AMBARI-14045) FE: Disallow to add the same host
 to different CG of the same service
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMBARI-14045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksandr Kovalenko updated AMBARI-14045:
-----------------------------------------
    Attachment: AMBARI-14045.patch

> FE: Disallow to add the same host to different CG of the same service
> ---------------------------------------------------------------------
>
>                 Key: AMBARI-14045
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14045
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.3
>            Reporter: Aleksandr Kovalenko
>            Assignee: Aleksandr Kovalenko
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-14045.patch
>
>
> {noformat}
> {
>   "href" : "http://c6401.ambari.apache.org:8080/api/v1/clusters/c/config_groups?ConfigGroup/tag=ZOOKEEPER&fields=*&_=1448282987731",
>   "items" : [
>     {
>       "href" : "http://c6401.ambari.apache.org:8080/api/v1/clusters/c/config_groups/53",
>       "ConfigGroup" : {
>         "cluster_name" : "c",
>         "description" : "",
>         "desired_configs" : [ ],
>         "group_name" : "2",
>         "hosts" : [
>           {
>             "href" : "http://c6401.ambari.apache.org:8080/api/v1/clusters/c/hosts/c6402.ambari.apache.org",
>             "host_name" : "c6402.ambari.apache.org"
>           }
>         ],
>         "id" : 53,
>         "tag" : "ZOOKEEPER"
>       }
>     },
>     {
>       "href" : "http://c6401.ambari.apache.org:8080/api/v1/clusters/c/config_groups/54",
>       "ConfigGroup" : {
>         "cluster_name" : "c",
>         "description" : "",
>         "desired_configs" : [ ],
>         "group_name" : "1",
>         "hosts" : [
>           {
>             "href" : "http://c6401.ambari.apache.org:8080/api/v1/clusters/c/hosts/c6401.ambari.apache.org",
>             "host_name" : "c6401.ambari.apache.org"
>           },
>           {
>             "href" : "http://c6401.ambari.apache.org:8080/api/v1/clusters/c/hosts/c6402.ambari.apache.org",
>             "host_name" : "c6402.ambari.apache.org"
>           }
>         ],
>         "id" : 54,
>         "tag" : "ZOOKEEPER"
>       }
>     }
>   ]
> }
> {noformat}
> As you can see, we have 2 config groups for ZooKeeper and both have c6402.ambari.apache.org as a host assigned to goup. We should disallow user to assign one host to more than one group of one service. Validation should be provided both on UI and BE side.
> STR:
> 1. Create two config grups (a and b) for some service and assign one host for each group.
> 2. Go to host details -> configs of some of host used in step 1.
> 3. Change group for this host (a -> b or b -> a).
> As a result host will be added to new group, but is not deleted from old one.


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