Bug 746680 - [RHEVM Admin GUI] Wrong content of 'Assign Logical Network' window in the cluster grid
Summary: [RHEVM Admin GUI] Wrong content of 'Assign Logical Network' window in the clu...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-webadmin
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Einav Cohen
QA Contact:
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-17 14:13 UTC by Kiril Nesenko
Modified: 2014-07-11 00:08 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-16 06:57:12 UTC
oVirt Team: ---

Attachments (Terms of Use)
screen_shot (291.79 KB, image/jpeg)
2011-10-17 14:13 UTC, Kiril Nesenko 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Kiril Nesenko 2011-10-17 14:13:08 UTC 
Created attachment 528546 [details]
screen_shot

Description of problem:
I have 8 logical networks in the cluster that are attached to the host. In the cluster grid click on 'Logical Networks' and quickly clicking on 'Assign Logical Networks', I am receiving the list of networks but it looks like they are not attached to the cluster(see the attachment). Clicking on 'OK' will detach logical networks from the cluster.

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

How reproducible:
Always

Steps to Reproduce:
1. Attach some networks to the cluster.
2. Click quickly on 'Assign Logical Networks' in the Cluster grid.
3.
  
Actual results:
Clicking on 'OK' will detach the networks from the cluster.

Expected results:
List of networks should be filled correct.

Additional info:
*see the attachment
Comment 1 Martin Pavlik 2012-05-18 12:34:48 UTC 
Issue can be reproduced with oVirt Enterprise Virtualization Engine Manager Version: 3.1.0_0001-9.el6ev
Comment 2 Itamar Heim 2012-12-16 06:57:12 UTC 
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.
Note You need to log in before you can comment on or make changes to this bug.