Setting on 3.3 but required farther discussion - as I recall tree refresh has two drawbacks: 1. It's an intensive operation since it scans a lot of information 2. Tree refresh collapses everything while I assume that this request want's to refresh while leaving the view hierarchy intact. Meaning what is currently expended should remain extended, same with collapsed, and the user must remain within the same selected scope. Einav, is this doable with the current technology we use for the tree?
Simon - your observations are correct: 1. indeed - we do intense search actions, and with all the performance issues - I am not sure if doing more of these is such a good idea. need to find a solution for this before handling tree-auto-refresh. 2. indeed - need to solve bug 684824 before handling tree-auto-refresh (filling "depends on" accordingly) Therefore, I am not sure that we will be able to handle it for 3.3 (not "devel_ack"ing yet).
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.
It is important to get this fixed, because it is really inconvenient for the user to not have the tree auto refreshed.
verified @ oVirt Engine Version: 3.5.0-0.0.master.20140715172114.git4687dc1.fc19
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. https://rhn.redhat.com/errata/RHSA-2015-0158.html