Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 7 Jul 2014 18:10:33 +0000 (UTC)
From: "Aleksandr Kovalenko (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12725800.1404756562445.13801.1404756633785@arcas>
In-Reply-To: <JIRA.12725800.1404756562445@arcas>
References: <JIRA.12725800.1404756562445@arcas>
Subject: [jira] [Created] (AMBARI-6405) Move Wizard: get stuck if wizard is
 running second time for the same component without page refresh
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Aleksandr Kovalenko created AMBARI-6405:
-------------------------------------------

             Summary: Move Wizard: get stuck if wizard is running second time for the same component without page refresh
                 Key: AMBARI-6405
                 URL: https://issues.apache.org/jira/browse/AMBARI-6405
             Project: Ambari
          Issue Type: Bug
          Components: client
    Affects Versions: 1.6.1
            Reporter: Aleksandr Kovalenko
            Assignee: Aleksandr Kovalenko
            Priority: Critical
             Fix For: 1.6.1


STR:

1. Run Move Wizard for some master component.
2. Do not click Complete button after all operation will be finished. Close wizard (confirm closing).
3. Without page refresh open wizard for the same master component and try it to reassign to another host (ex. back to the previous host).

Wizard will get stuck, as source host for master component will be calculated incorrectly.

This issue is related to host components mapper. After first running of move wizard in the model there were 2 masters one with host before moving and the new one. Old host component was deleted on server but UI model still contains it. And it brakes algorithm of calculating source host on assign master step.


--
This message was sent by Atlassian JIRA
(v6.2#6252)