Bug 858166
Summary: | PRD34 - [RFE] webadmin - centralized refreshing logic | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Pavel Stehlik <pstehlik> | |
Component: | ovirt-engine-webadmin-portal | Assignee: | Alexander Wels <awels> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Pavel Stehlik <pstehlik> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 3.1.0 | CC: | aberezin, acathrow, adahms, awels, cpelland, djasa, ecohen, iheim, jkt, pstehlik, Rhev-m-bugs, tjelinek, vszocs | |
Target Milestone: | --- | Keywords: | FutureFeature | |
Target Release: | 3.4.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ux | |||
Fixed In Version: | ovirt-3.4.0-alpha1 | Doc Type: | Enhancement | |
Doc Text: |
Previously, making a change to an object in the Administration Portal and attempting to perform subsequent actions on that object or related objects would result in an error under certain conditions. This was caused by the logic used to refresh objects in the Administration Portal, whereby objects would only be fully refreshed after reaching the next refresh interval following a change. Now, the logic used to refresh objects has been revised so that objects are fully refreshed immediately following an action, making it possible to perform subsequent actions on those objects without issue.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1049996 (view as bug list) | Environment: | ||
Last Closed: | 2014-06-12 14:04:10 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 879662, 1049996 |
Description
Pavel Stehlik
2012-09-18 08:41:55 UTC
I noticed the same issue when working with VM snapshots (e.g. seeing that the commit was finished but the VM is not able to start for another 5 seconds) and it's really annoying - therefore I propose to to fix it in 3.1. Setting placeholder for 3.2 and (potential) .z From code perspective, the refresh logic in 3.1 (GWT technology) is the same as in 3.0 (WPF technology). This is because common UI logic (also known as "uicommon") was re-used in 3.1 by converting C# code into Java. By design, different parts of GUI are refreshed independently from other parts. This results in multiple HTTP requests against the backend, as each GUI component tries to fetch its "own" data. If one GUI component has refresh rate X and another component has refresh rate Y, when X != Y, GUI as a whole is generally "not in sync" with regard to current data. In 3.0 (WPF technology), communication between GUI and backend was synchronous. In 3.1 (GWT technology), communication between GUI and backend is asynchronous. This fact makes the refresh logic problem more visible. Short-term solution: at certain moments (e.g. closing a dialog with OK button, clicking action button in a data grid), enforce all GUI components to refresh their data immediately. This way the GUI will be "in sync" with regard to current data at certain key moments during the runtime. Long-term solution: re-write refresh logic, potentially optimizing the number of HTTP requests against the backend. ovirt 3.4.0 alpha has been released Closing as part of 3.4.0 |