Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Wed, 4 Jul 2012 21:55:19 +0000 (UTC)
From: "Vinod Kumar Vavilapalli (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <1321598180.6485.1341438919491.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <749534335.5552.1337197269152.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (AMBARI-273) Fix TxnProgressWidget To Show Failed
 States When No SubTxn Is In Progress
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vinod Kumar Vavilapalli updated AMBARI-273:
-------------------------------------------

    Affects Version/s:     (was: ambari-186)
                       0.9.0
    
> Fix TxnProgressWidget To Show Failed States When No SubTxn Is In Progress
> -------------------------------------------------------------------------
>
>                 Key: AMBARI-273
>                 URL: https://issues.apache.org/jira/browse/AMBARI-273
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 0.9.0
>            Reporter: Varun Kapoor
>            Assignee: Varun Kapoor
>            Priority: Critical
>             Fix For: 0.9.0
>
>         Attachments: AMBARI-273.patch
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> Rework TxnProgressWidget's iteration logic to be robust enough to not skip failed/pending states when a subTxn fails and there's nothing "InProgress".
> The way this manifests right now is that on failure, since the orchestrator's subTxn info doesn't (any longer) include an "InProgress" state, only the "Done" states show, and everything after that is skipped over in the hunt-for-the-first-InProgress-state loop, which is pretty darn confusing for the user.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira