Bug 773694 - Core: we can randomly add the same lun to two different domains in the same DC
Summary: Core: we can randomly add the same lun to two different domains in the same DC
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.1.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: 3.2.0
Assignee: Ayal Baron
QA Contact: Haim
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-12 16:02 UTC by Dafna Ron
Modified: 2016-02-10 16:50 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-18 10:53:18 UTC
oVirt Team: Storage
Target Upstream Version:


Attachments (Terms of Use)
logs (610.90 KB, application/x-gzip)
2012-01-12 16:02 UTC, Dafna Ron
no flags Details

Description Dafna Ron 2012-01-12 16:02:37 UTC
Created attachment 552444 [details]
logs

Description of problem:

logging into a lun that is already a part of a domain should be blocked by backend, but I was able several times to add the same lun to two different domains which were apart of the same Data Center. 

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

vdsm-4.9.2-0.65.gitf945dc2.fc16.x86_64
libvirt-0.9.6-4.fc16.x86_64
ovirt-engine-backend-3.0.0_0001-7.fc16.x86_64

How reproducible:

randomly

Steps to Reproduce:
1. create several iscsi luns
2. add a domain using 3 luns
3. add a second domain using other luns+1 or 2 of the target luns used in previous domain. 
  
Actual results:

you will randomaly be able to add the same target to two different domains (sharing the same DC)

Expected results:

we should not be able to even see the targets in the target tab but if we do operation should fail. 

Additional info: full logs

Comment 1 Dafna Ron 2012-01-12 16:05:16 UTC
Dafna-03 is the shared lun

Comment 6 Haim 2012-12-18 10:53:18 UTC
Apparently not relevant.


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