Bug 865484

Summary: webadmin: no vm name is given when we fail export because vm is in preview
Product: Red Hat Enterprise Virtualization Manager Reporter: Dafna Ron <dron>
Component: ovirt-engine-webadmin-portalAssignee: Tomas Jelinek <tjelinek>
Status: CLOSED WONTFIX QA Contact: Pavel Stehlik <pstehlik>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.1.0CC: acathrow, ecohen, iheim, jkt, michal.skrivanek, Rhev-m-bugs, tjelinek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-29 11:16:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
log and screenshot none

Description Dafna Ron 2012-10-11 14:50:15 UTC
Created attachment 625552 [details]
log and screenshot

Description of problem:

I tried exporting multiple vm's when one of the vms was in preview. 
the export for that vm failed but we do not show which one: 

Error while executing action: Cannot export VM. VM is previewing a Snapshot.

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

si20 upgraded from 3.0

How reproducible:

100%

Steps to Reproduce:
1. export multiple vms while one of the vms is in preview on a snapshot
2.
3.
  
Actual results:

we fail to export the vm but do not specify which one

Expected results:

we should specify which vm cannot be exported. 

Additional info: engine log + screen shot

this seems to be a UI issue since I cannot find a CanDoAction in the engine log but attaching engine log just in case its still engine.

Comment 1 Tomas Jelinek 2012-10-18 09:45:50 UTC
Well, there are many places where it is done this way. Basically all the messages are done in this way - e.g. try export vm twice, you will see "Error while executing action: Cannot export VM. VM with the same identifier already exists."

I would say that if we want to fix this, we should fix it for all of the occurrences not only for this one.

Comment 2 Michal Skrivanek 2012-10-18 09:48:51 UTC
although not nice, we should address this globally as Tomas says. Pushing out of 3.1 to fix this properly unless you want to do an one-off

Comment 3 Itamar Heim 2013-12-29 11:16:31 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.