Varun Kapoor created AMBARI-194:
-----------------------------------
Summary: 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
Priority: Critical
Fix For: ambari-186
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
