[
https://issues.apache.org/jira/browse/AMBARI-12458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632740#comment-14632740
]
Hadoop QA commented on AMBARI-12458:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12745993/AMBARI-12458.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/3423//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3423//console
This message is automatically generated.
> Blueprint based deployments record same host multiple times if it re-registers
> ------------------------------------------------------------------------------
>
> Key: AMBARI-12458
> URL: https://issues.apache.org/jira/browse/AMBARI-12458
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, blueprints
> Affects Versions: 2.1.0
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12458.patch
>
>
> The pre-conditions are actual number of hosts registered is less than the
> number of hosts expected when predicates are used.
> e.g.
> {noformat}
> {
> "name": "host_group_2",
> "host_count": "3",
> "host_predicate": "Hosts/host_name.matches(workernode.*)"
> }
> {noformat}
> The problem is that the logical request never completes. While it is
> expected, it locks up operations such as start-all and stop-all for the "All
> Services" menu. We should verify what other operations aren't getting
> blocked. It will be an UI change to not restrict the operations.
> If the above condition is true and one of the hosts goes through a
> re-registration you end up with the open logical request getting associated
> with the host that re-registered. This results in a incorrect mapping but it
> does not result in any form of duplicate commands.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
