Description of problem: 'No VM Import to display'/'No Template Import to display' appear for little while when I try to check exported VMs/exported Templates on an export domain. This seems like bug, normally I would expect to see those little black dots/boxes telling me it is loading data... Version-Release number of selected component (if applicable): sf5 How reproducible: most of the time Steps to Reproduce: 1. have some vms and templates on a export domain 2. check the list couple of times 3. Actual results: most of the time 'No VM Import to display'/'No Template Import to display', then the list appears Expected results: those little black dots/boxes telling me it is loading data... Additional info:
I've heard similar complaints in other dialogs...Einav, do you know, is this a general issue?
(In reply to comment #1) > I've heard similar complaints in other dialogs...Einav, do you know, is this > a general issue? not familiar with this issue - I will take it. Thanks.
Alex - can you please take a quick look and estimate how difficult it is to solve? We would want to have the "squares" progress-animation when activating a certain tab/sub-tab until the initial results for that tab/sub-tab have arrived from the backend. Once arrived - we should put "no items to display" (if results are empty) or the items themselves (if results are not empty).
Einav, That shouldn't be terribly difficult to fix, what I think is happening is that the page is displayed before the query to populate the data is made. At that point there is NO data to display, until the query is done. We might have to rethink where we add the No items to display message. Right now we do it in the constructor of the table, might have to move it to the success/failure of the query.
*** Bug 962592 has been marked as a duplicate of this bug. ***
ok, is6.
This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2014-0038.html