Bug 1281729 - external VM name clash
Summary: external VM name clash
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 3.5.5
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: bugs@ovirt.org
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks: 1272099
TreeView+ depends on / blocked
 
Reported: 2015-11-13 10:17 UTC by Michal Skrivanek
Modified: 2022-04-13 14:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-14 11:25:11 UTC
oVirt Team: Virt
Embargoed:
sbonazzo: ovirt-4.3-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-45658 0 None None None 2022-04-13 14:36:23 UTC

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
Note You need to log in before you can comment on or make changes to this bug.