Bug 1950730

Summary:	Remove old Cinder integration from the REST-API
Product:	[oVirt] ovirt-engine	Reporter:	Eyal Shenitzky <eshenitz>
Component:	BLL.Storage	Assignee:	shani <sleviim>
Status:	CLOSED CURRENTRELEASE	QA Contact:	sshmulev
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.4.6	CC:	ahadas, bugs, eshames
Target Milestone:	ovirt-4.5.0	Keywords:	ZStream
Target Release:	4.5.0	Flags:	pm-rhel: ovirt-4.5?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.5.0	Doc Type:	Removed functionality
Doc Text:	This patch removes the ability to create/use old cinder integration using the REST API.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-04-28 09:26:34 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 Eyal Shenitzky 2021-04-18 08:13:11 UTC

Description of problem:
The old Cinder integration (through External Providers->Openstack Block Storage) is deprecated and was replaced by Cinderlib integration (Managed Block Storage), the old integration should be removed from the REST-API.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 shani 2021-10-31 08:26:03 UTC

 verification steps: Send the following requests on the REST API:

    GET/POST http://localhost:8080/ovirt-engine/api/openstackvolumeproviders
    DELETE http://localhost:8080/ovirt-engine/api/openstackvolumeproviders/1231231231321313 

Result:
<pre>java.lang.RuntimeException: org.jboss.resteasy.spi.UnhandledException: java.lang.UnsupportedOperationException: Cinder integration replaced by Managed Block Storage.
Please use Managed Block Storage for creating Cinderlib based storage domain.

Comment 5 Sandro Bonazzola 2022-04-28 09:26:34 UTC

This bugzilla is included in oVirt 4.5.0 release, published on April 20th 2022.

Since the problem described in this bug report should be resolved in oVirt 4.5.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.