Bug 800465

Summary: Cannot choose iSCSI domain format when creating new domain to uninitalized DC
Product: [Retired] oVirt Reporter: Jakub Libosvar <jlibosva>
Component: ovirt-engine-webadminAssignee: Einav Cohen <ecohen>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: acathrow, ecohen, iheim, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-07 08:59:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Screenshot none

Description Jakub Libosvar 2012-03-06 14:14:42 UTC
Created attachment 567958 [details]
Screenshot

Description of problem:
After new DC is created and one wants to create and attach new domain V1 to DC version 3.0, he can't cause domain format listbox is inactive.

Version-Release number of selected component (if applicable):
ovirt-engine-webadmin-portal-3.0.0_0001-3.git4364f1b.fc16.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Create new DC version 3.0
2. Try to create new storage domain V1 to DC created in step 1
  
Actual results:
Domain format is inactive

Expected results:
User can choose domain format

Additional info:
Screenshot attached

When storage domain is created without implicitly attaching to some DC, domain format is listbox active.

Comment 1 Itamar Heim 2012-03-06 22:30:34 UTC
I'm not sure if there is no hidden bug here, but i don't see a reason we'll support adding a V1 storage domain to a 3.0 DC (maybe it was even done on purpose to block this).
iirc, V1 block storage domain is only relevant if you would join a 2.2 cluster to the DC, and a 3.0 DC can't have a 2.2 cluster anyway.
Ayal?

Comment 2 Einav Cohen 2012-03-07 08:59:42 UTC
according to the GUI code, it seems that we explicitly (by design) allow creating only V2 data storage domains in case the selected storage type is iSCSI/FC and the selected (uninitialized) DC's compatibility version is greater than or equal to 3.0.

Although it is technically possible to create a V1 storage domain in a 3.0 Data Center, the user doesn't have a real reason to do that (also detailed in Comment #1). IIRC, you can do that via the api, if you would really like to do that.

Closing on NOT-A-BUG.