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

Bug 1786569

Summary:	Export VM to data domain with the same name fails with no clear error in the UI
Product:	[oVirt] ovirt-engine	Reporter:	Evelina Shames <eshames>
Component:	BLL.Storage	Assignee:	Benny Zlotnik <bzlotnik>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Evelina Shames <eshames>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.4.0	CC:	bugs, dfodor
Target Milestone:	ovirt-4.4.0	Flags:	pm-rhel: ovirt-4.4+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-ui-extensions-1.0.13-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-20 19:59:35 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 Evelina Shames 2019-12-26 09:43:17 UTC

Description of problem:
Export VM to data domain with the same name fails with no clear error in the UI

Version-Release number of selected component (if applicable):
engine-4.4.0-0.13
ovirt-engine-ui-extensions-1.0.11-1

How reproducible:
Always

Steps to Reproduce:
1.Try to export VM with the same name


Actual results:
Operation fails without clear error in the UI

Expected results:
Operation should be blocked with clear error in the UI when trying to export with the same name.

Additional info:

Comment 1 RHV bug bot 2020-01-24 19:49:25 UTC

INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[No relevant external trackers attached]

For more info please contact: infra

Comment 2 Evelina Shames 2020-03-31 11:55:05 UTC

Verified on engine-4.4.0-0.25.master.el8ev.

Comment 3 Sandro Bonazzola 2020-05-20 19:59:35 UTC

This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

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