Bug 1281729

Summary:	external VM name clash
Product:	[oVirt] ovirt-engine	Reporter:	Michal Skrivanek <michal.skrivanek>
Component:	BLL.Virt	Assignee:	bugs <bugs>
Status:	CLOSED WONTFIX	QA Contact:	meital avital <mavital>
Severity:	medium	Docs Contact:
Priority:	high
Version:	3.5.5	CC:	bugs, mgoldboi
Target Milestone:	---	Keywords:	UserExperience
Target Release:	---	Flags:	sbonazzo: ovirt-4.3-
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-14 11:25:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1272099

Description Michal Skrivanek 2015-11-13 10:17:49 UTC

when a VM "x" previously used in the system becomes external (as a result of a problem, unclean host removal, etc) it is imported as "external-x". Then if I again create a brand new VM "x" without removing "external-x" and the same situation happens, engine will try to add "external-x" again since IDs are different, only to fail miserably on a name conflict.

we should have some protection for these cases. Moreover I think when I name my regular VM as "external-x" I'm going to have the same trouble

Comment 2 Michal Skrivanek 2016-12-21 09:08:41 UTC

The bug was not addressed in time for 4.1. Postponing to 4.2

Comment 3 Ryan Barry 2018-11-14 11:25:11 UTC

This will not make it in a reasonable time. Please re-open if you still feel this should be fixed