Bug 841127

Summary:	[rhevm] upgrading to V3 storage domains breaks backward compatibility scripts
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Haim <hateya>
Component:	ovirt-engine	Assignee:	Miki Kenneth <mkenneth>
Status:	CLOSED NOTABUG	QA Contact:	Haim <hateya>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.1.0	CC:	amureini, dyasny, iheim, lpeer, Rhev-m-bugs, sgordon, sgrinber, yeylon, ykaul
Target Milestone:	---	Keywords:	Documentation
Target Release:	3.1.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	storage
Fixed In Version:		Doc Type:	Release Note
Doc Text:	All new storage domains created in Red Hat Enterprise Virtualization 3.1 must be of type "V3". This causes existing scripts that call the REST API to create storage domains, specifying type "V2" to fail.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-08-13 15:10:40 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:

Description Haim 2012-07-18 08:42:59 UTC

Description of problem:

as per our upgrading of storage domain format from v2 to v3 domains, we need to consider that it may break backward compatibility REST scripts while in the past, we were required to pass v2 and now we fail to do so upon creation of new 3.1 storage domain as v3 is required. 

we need to document this case.

Comment 1 Stephen Gordon 2012-08-09 13:39:37 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
All new storage domains created in Red Hat Enterprise Virtualization 3.1 must be of type "V3". This causes existing scripts that call the REST API to create storage domains, specifying type "V2", to fail.

Comment 2 Itamar Heim 2012-08-13 15:10:40 UTC

closing - release note bugs are monitored by their flag, not status