Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Tue, 18 Dec 2012 23:44:12 +0000 (UTC)
From: "ARUN KUMAR KANDREGULA (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <JIRA.12624547.1355872555668.26205.1355874252586@arcas>
In-Reply-To: <JIRA.12624547.1355872555668@arcas>
References: <JIRA.12624547.1355872555668@arcas>
Subject: [jira] [Updated] (AMBARI-1102) Error handling when errors are
 encountered during preparation for deploy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

ARUN KUMAR KANDREGULA updated AMBARI-1102:
------------------------------------------

    Attachment: AMBARI-1102.patch
    
> Error handling when errors are encountered during preparation for deploy
> ------------------------------------------------------------------------
>
>                 Key: AMBARI-1102
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1102
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.2.0
>            Reporter: ARUN KUMAR KANDREGULA
>            Assignee: ARUN KUMAR KANDREGULA
>              Labels: client, installer
>             Fix For: 1.2.0
>
>         Attachments: AMBARI-1102.patch
>
>
> Currently, if any errors are encountered during preparation for deploy, the user is taken to the deploy page and the hosts will be shown as "Waiting" but nothing happens. This is bad UX.
> At a minimum, we should prevent the user from proceeding and display an appropriate error message if any error is encountered after "Deploy" is clicked, but before we transition to Step 9.
> We should also think about how a user can recover from this situation.
> At this point, the deploy has not initiated, but certain API calls may have succeeded, so we may have incomplete info in the database. Currently there's no convenient way to "rollback".
> We can either ask the user to clean the slate by reinitializing the database and try again (should succeed if the original problem was temporary).
> We can also build more logic in the UI to retry, check if records already exist, etc...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira