Description of problem:
It should not change the virtual machines count every time when enter dashboard page even if there is no new changes. It always changes from 0 Running to X Running when enter the dashboard page. It should be better just stay on X Running when there is no changes.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install rhev-hypervisor7-ng-3.6-20160506.0.el7
2. Disable NetworkManager service.
3. Create a virtual machine.
4. Check the dashboard.
1. It always change from 0 Running to 1 Running when enter the dashboard page.
1. It should keep 1 Running until other changes came.
There is no practical way to fix this.
It's a stateless application which updates the count when a dbus call returns. We cannot keep the state inbetween different pages.
Use some placeholder text (but that will also get updated almost immediately).
Use redux as a backend, but that's low priority.
Fabian, can you devel_ack- this, or retarget to 4.1 (where we'll have time to implement redux)?
I tested -- we can block showing that element until we get a response. This way the count of VMs will not change from 0->$number (though starting/stopping VMs will still change the count)
I'd really rather not block the entire page, though, for a variety of reasons.
Does that work?
Just for considerations, what about showing a placeholder until the count is available, i.e.
But only showing the element once the count is available works for me too.
1. Install rhev-hypervisor7-ng-3.6-20160527.0
2. Create a virtual machine.
3. Check the dashboard.
1. The Virtual Machines's summary page is blocked before get the latest status.
For this issue, the vm's whole summary page is blocked before get the latest status. So every time when enter this page, the page will changed from without VM's column to have it. Do you think it's better to add a loading icon as a placeholder when waiting of a update?
This should be a small UX change.
I am ok with adding a small loading icon (I'll push a patch up), but it shouldn't be necessary for verification of this bug, in my opinion.
Verify this issue due to comment#4&5.
oVirt 4.0.0 has been released, closing current release.