Bug 833120 - webadmin: when creating a direct lun for a vm I am able to select a different data center which the vm is not located on and I have no cluster selection
Summary: webadmin: when creating a direct lun for a vm I am able to select a different...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.1.0
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ---
: 3.1.0
Assignee: Tal Nisan
QA Contact: Dafna Ron
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-18 16:07 UTC by Dafna Ron
Modified: 2016-02-10 17:10 UTC (History)
8 users (show)

Fixed In Version: SI9
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-04 20:04:42 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
logs and screen shot (1.03 MB, application/x-gzip)
2012-06-18 16:10 UTC, Dafna Ron
no flags Details

Description Dafna Ron 2012-06-18 16:07:45 UTC
Description of problem:

when creating a direct lun from the disks sub tab, I am able to select a different DC than the DC selected for the vm. 
once I start the vm it will start in the correct DC/cluster but I still have an open session to it in the wrong DC. 

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

si6

How reproducible:

100%

Steps to Reproduce:
1. create two DC's
2. add a vm on one of the DC's
3. create a direct lun and select the second DC in the selection roller. 
4. run the vm 
  
Actual results:

lun will be logged in on both Data centers/clusters

Expected results:

when creating a direct lun for a specific vm we should filter other DC's/clusters from the ones vm was created on. 

Additional info:screen shot+logs

Comment 1 Dafna Ron 2012-06-18 16:10:56 UTC
Created attachment 592697 [details]
logs and screen shot

Comment 2 Tal Nisan 2012-06-26 12:38:31 UTC
http://gerrit.ovirt.org/5710

Comment 3 Dafna Ron 2012-07-08 15:23:50 UTC
Verified on si9.1


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