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

Bug 1503031

Summary:	Response body of file based storage domain creation due to dirty path does not have an indication of which domain resides on that path
Product:	[oVirt] ovirt-engine	Reporter:	Elad <ebenahar>
Component:	BLL.Storage	Assignee:	Ahmad Khiet <akhiet>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Yosi Ben Shimon <ybenshim>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.2.0	CC:	bugs, frolland, tnisan
Target Milestone:	ovirt-4.3.0	Keywords:	Automation, EasyFix, StudentProject
Target Release:	---	Flags:	rule-engine: ovirt-4.3+
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.3.0_rc	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-13 07:43:16 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 Elad 2017-10-17 08:36:40 UTC

Description of problem:
When file based storage domain creation fails on Status: 409, Reason: Conflict, the response body in REST doesn't contain details about the domain that resides on the path. This information is valid in the same scenario with block based storage domains.



Block domain:

	Status: 409
	Reason: Conflict
	Detail: [Cannot add Storage. The following LUNs are already part of existing storage domains: 3514f0c5a51600274 (sd_TestCase19016_REST_ISCS_1601185285).]



File domain:

	Status: 409
	Reason: Conflict
	Detail: [Cannot add Storage Connection. Storage connection already exists.]


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

How reproducible:
ovirt-engine-4.2.0-0.0.master.20171013142622.git15e767c.el7.centos.noarch
ovirt-engine-restapi-4.2.0-0.0.master.20171013142622.git15e767c.el7.centos.noarch


Steps to Reproduce:
1. Create NFS domain
2. Try to create a domain on the same path via REST


Actual results:
The response body doesn't contain the name of the domain that reside on the path

Expected results:
The response body should contain the domain name as it is reported for block domains

Comment 1 Juan Hernández 2017-10-17 09:09:47 UTC

The error messages aren't generated by the API, but by the backend, so I am moving to the corresponding component.

Comment 3 Yosi Ben Shimon 2019-01-31 11:32:22 UTC

Tested using:
ovirt-engine-4.3.0.2-0.1.el7.noarch

RestApi request:

- URL:
https://storage-ge-16.scl.lab.tlv.redhat.com/ovirt-engine/api/storagedomains

- Request body:
<storage_domain>
  <name>myNfs</name>
  <type>data</type>
  <description>My nfs</description>
  <storage>
    <type>nfs</type>
    <address>yellow-vdsb.qa.lab.tlv.redhat.com</address>
    <path>/Storage_NFS/storage_local_ge16_nfs_1</path>
  </storage>
  <host>
    <name>host_mixed_2</name>
  </host>
</storage_domain>

Actual result:
The response is:
<fault>
    <detail>[Cannot add Storage Connection. Storage connection 154bcb10-10cc-449a-af88-244a9e9473c5 already exists for nfs_1.]</detail>
    <reason>Operation Failed</reason>
</fault>


Moving to VERIFIED

Comment 4 Sandro Bonazzola 2019-02-13 07:43:16 UTC

This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.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.