Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 895601

Summary: engine: we are able to create a V2 domain on RHEL6.4 host (vdsm-4.10.2-3.0.el6ev.x86_64)
Product: Red Hat Enterprise Virtualization Manager Reporter: Dafna Ron <dron>
Component: ovirt-engineAssignee: Ayal Baron <abaron>
Status: CLOSED WONTFIX QA Contact: Dafna Ron <dron>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: acathrow, amureini, dyasny, hateya, iheim, lpeer, Rhev-m-bugs, yeylon, ykaul
Target Milestone: ---Keywords: Regression, Reopened
Target Release: 3.3.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-04 15:26:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 856583    
Attachments:
Description Flags
logs none

Description Dafna Ron 2013-01-15 15:58:51 UTC
Created attachment 678856 [details]
logs

Description of problem:

I am working on 3.2 setup. 
I was able to create a V2 domain with a RHEL2.4 host (vdsm-4.10.2-3.0.el6ev.x86_64)

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

sf3
vdsm-4.10.2-3.0.el6ev.x86_64

How reproducible:

100%

Steps to Reproduce:
1. in 3.2 rhevm, storage tab -> new domain -> select "None" 
2. select iscsi with V2 domain -> connect to target
3. press OK
  
Actual results:

domain is created 

Expected results:

we should have a CanDoAction 

Additional info: logs

Comment 4 Allon Mureinik 2013-01-16 10:47:14 UTC
ykaul - pending QA ack/nack on bug 826364 .

If we support 3.0 DCs on RHEVM 3.2, this is not a bug.
If we don't, we will block in CDA.

Comment 13 Allon Mureinik 2013-04-03 11:12:17 UTC
DC=none is a re-initialize flow.
I can have a DC 3.0 in a 3.2/3.3 system, so this must be supported.

Comment 14 Dafna Ron 2013-04-03 11:30:41 UTC
if the host selected to create the domain is part of a 3.2 DC/Cluster there is no reason to create the V2 domain even with the reinitialize flow since the pool has already been upgraded to v3.

Comment 15 Haim 2013-04-04 15:26:09 UTC
We see no reason blocking this option. 
Please let us know if we are not consistent in other similar flows.