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

Bug 1096762

Summary: [User Portal] When VM's snapshot delete is in progress, main grid still shows 'Up' action available
Product: Red Hat Enterprise Virtualization Manager Reporter: Jiri Belka <jbelka>
Component: ovirt-engine-userportalAssignee: Nobody <nobody>
Status: CLOSED NOTABUG QA Contact: Pavel Stehlik <pstehlik>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.4.0CC: acathrow, amureini, ecohen, gklein, iheim, ofrenkel, Rhev-m-bugs, yeylon
Target Milestone: ---   
Target Release: 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-14 10:35:25 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:
Attachments:
Description Flags
screenshot none

Description Jiri Belka 2014-05-12 11:55:50 UTC 
Created attachment 894666 [details]
screenshot

Description of problem:
When VM's snapshot delete is in progress, main grid still shows 'Up' action available. This is odd.

* VM state icon in main grid should probably be 'in-progress' state (not sure)????
* 'UP' action button should be disabled as clicking the button causes 'Error while executing action' dialog (operation in progress).

Is this just side-effect of UI refresh issue (BZ1071877) or is this separate issue?

See screenshot.

Version-Release number of selected component (if applicable):
av9/rhevm-userportal-3.4.0-0.18.el6ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. have a snapshot and delete it
2.
3.

Actual results:
action button available even the action cannot be executed anyway + probably wrong VM state button in main grid

Expected results:
'Up' button should be disabled if the action cannot be executed + probably in-progress button in main grid for the VM

Additional info:
Comment 1 Omer Frenkel 2014-05-13 06:36:58 UTC 
this is by design, there was a request not to lock globally the vm on image operations (before the vm would move to 'image-locked' as you suggest here),
as some operations could still be performed (for example you can still add NICs during images operations)
Comment 2 Allon Mureinik 2014-05-14 10:35:25 UTC 
(In reply to Omer Frenkel from comment #1)
> this is by design, there was a request not to lock globally the vm on image
> operations (before the vm would move to 'image-locked' as you suggest here),
> as some operations could still be performed (for example you can still add
> NICs during images operations)

Closing according to Omer's comment above.