Bug 987897 - VM - network interfaces subtab has a delayed refresh and displays wrong info for a while
Summary: VM - network interfaces subtab has a delayed refresh and displays wrong info ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-webadmin
Version: 3.3
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: m1
: 3.3.2
Assignee: Lior Vernia
QA Contact:
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-24 11:41 UTC by Alissa
Modified: 2015-05-05 01:43 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-19 14:24:30 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)
wrong nics refresh (87.51 KB, image/png)
2013-07-24 11:41 UTC, Alissa
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 20082 0 None None None Never

Description Alissa 2013-07-24 11:41:00 UTC
Created attachment 777744 [details]
wrong nics refresh

Description of problem:
When selecting a vm with 2 nics and then moving to a vm with one nic,
it still displays 2 nics, while one of them belongs to previous vm, and another to the current.
After couple of seconds it refreshes properly and shows only one nic.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.select vm with 2 nics
2.move to network interfaces subtab
3.select vm with 1 nic
4.network interfaces subtab displays 2 nics, both named nic1 - one from current vm, the other from previous
5. wait 2-3 seconds, it refreshes and one of them disappears.

Actual results:


Expected results:
display the correct nics from the beginning.


Additional info:

Comment 1 Sandro Bonazzola 2013-12-13 16:01:58 UTC
rc build done, moving to ON_QA, packages will be available on updates-testing repository.

Comment 2 Sandro Bonazzola 2013-12-19 14:24:30 UTC
oVirt 3.3.2 has been released resolving the problem described in this bug report.


Note You need to log in before you can comment on or make changes to this bug.