Bug 748261 - Backend [TEXT]: when trying to import a vm with the same name and different id the error message is that the vm with the same id already exists
Summary: Backend [TEXT]: when trying to import a vm with the same name and different i...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: unspecified
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: lpeer
QA Contact:
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-23 16:31 UTC by Dafna Ron
Modified: 2012-12-12 10:42 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-12 10:42:52 UTC
oVirt Team: ---


Attachments (Terms of Use)
log (263.63 KB, application/x-gzip)
2011-10-23 16:31 UTC, Dafna Ron
no flags Details

Description Dafna Ron 2011-10-23 16:31:10 UTC
Created attachment 529693 [details]
log

Description of problem:

error message presented to user when trying to export a vm with the same name is that there is already a vm with the same id - this is wrong. 
we check both name and vm id so each error should have its own text. 

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

How reproducible:
100%

Steps to Reproduce:
1. create a VM
2. export the VM
3. remove the VM and create a new vm by the same name 
4. try to export the vm

Actual results:

we get a CanDoAction from backend that vm id already exists. 

011-10-23 18:20:25,240 WARN  [org.ovirt.engine.core.bll.ImportVmCommand] (pool-11-thread-962) CanDoAction of action ImportVm failed. Reasons:VM_CANNOT_IMPORT_VM_EXISTS,$VmName 
NFS-02,VAR__ACTION__IMPORT,VAR__TYPE__VM

Expected results:

since the ID does not exists (it's a completely different VM with a different id) but the name does exists we should change the text of this alert. 


Additional info:rhevm log

Comment 2 Itamar Heim 2012-12-12 10:42:52 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.


Note You need to log in before you can comment on or make changes to this bug.