[jira] [Assigned] (AMBARI-194) Avoid TxnProgressWidget Getting Stuck In An Infinite Loop

["Varun Kapoor (JIRA)" <ji...@apache.org>]

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

Varun Kapoor reassigned AMBARI-194:
-----------------------------------

    Assignee: Varun Kapoor
    
> Avoid TxnProgressWidget Getting Stuck In An Infinite Loop
> ---------------------------------------------------------
>
>                 Key: AMBARI-194
>                 URL: https://issues.apache.org/jira/browse/AMBARI-194
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: ambari-186
>            Reporter: Varun Kapoor
>            Assignee: Varun Kapoor
>            Priority: Critical
>             Fix For: ambari-186
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> php/frontend/fetchTxnProgress.php's response JSON checks that at least one subTxn is in progress, or it sets the top-level 'progress' key to null. The JS checks for this null-ness before deciding to swap the loading image for the list of progress states. 
> Sadly, when the backend txn is a no-op (for instance, when a service is already started but a user starts it again from the Manage Services page), none of the subTxns will be in-progress, causing this condition to be triggered. Thus, no-ops lead to the loading image showing forever, with no way for users to break the cycle, which is pretty darn bad.

--
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