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

Bug 872916

Summary: [TEXT] webadmin: running move from disks tab while vm is powering up yields an unclear error message from canDoAction
Product: Red Hat Enterprise Virtualization Manager Reporter: Dafna Ron <dron>
Component: ovirt-engine-webadmin-portalAssignee: Daniel Erez <derez>
Status: CLOSED CURRENTRELEASE QA Contact: Dafna Ron <dron>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.1.0CC: abaron, dyasny, ecohen, hateya, iheim, Rhev-m-bugs, sgrinber, ykaul
Target Milestone: ---   
Target Release: 3.2.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: storage
Fixed In Version: sf3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:
Bug Depends On:    
Bug Blocks: 915537    
Attachments:
Description Flags
log none

Description Dafna Ron 2012-11-04 08:56:17 UTC
Created attachment 637918 [details]
log

Description of problem:

the move tab is not greyed out in the disks tab while vm is powering up
it is greyed out from the vm's tab. 

when you try to move the disk we would get an incorrect error message: 

Error while executing action: Cannot move Virtual Machine Disk. At least one of the VMs is not down.

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

si23

How reproducible:

100%

Steps to Reproduce:
1. run a vm
2. move disk from disks tab while vm is powering up
3.
  
Actual results:

1. move tab is not greyed out in disks tab but greyed out in vm's tab
2. incorrect text on canDoAction

Expected results:

1. we should be consistent and grey out the move button until the vm is up
2. fix CanDoAction for API

Additional info: log

Comment 1 Ayal Baron 2012-11-07 22:22:17 UTC
(In reply to comment #0)
> Created attachment 637918 [details]
> log
> 
> Description of problem:
> 
> the move tab is not greyed out in the disks tab while vm is powering up
> it is greyed out from the vm's tab. 
> 
> when you try to move the disk we would get an incorrect error message: 
> 
> Error while executing action: Cannot move Virtual Machine Disk. At least one
> of the VMs is not down.
> 
> Version-Release number of selected component (if applicable):
> 
> si23
> 
> How reproducible:
> 
> 100%
> 
> Steps to Reproduce:
> 1. run a vm
> 2. move disk from disks tab while vm is powering up
> 3.
>   
> Actual results:
> 
> 1. move tab is not greyed out in disks tab but greyed out in vm's tab
> 2. incorrect text on canDoAction
> 
> Expected results:
> 
> 1. we should be consistent and grey out the move button until the vm is up

not going to happen as disks tab is a main tab and it runs a query every 5s. Fetching VM status for all the VMs of all the disks is just not realistic.

> 2. fix CanDoAction for API
> 
> Additional info: log

Comment 2 Ayal Baron 2012-12-19 11:07:12 UTC
Need to change the canDoAction to something like: "Move disk is only permitted while VM is either in 'Down' or 'Up' state"

Comment 3 Daniel Erez 2012-12-30 20:09:09 UTC
patch merged:
http://gerrit.ovirt.org/#/c/10154/
Change-Id: Iadcffa5748b58b1af40535b0447487dde6c2d6cb

Comment 4 Dafna Ron 2013-01-07 16:49:25 UTC
Error: Cannot move Virtual Machine Disk. VM TEST1 must be in status Down or Up.

verified on sf3

Comment 5 Itamar Heim 2013-06-11 09:06:54 UTC
3.2 has been released

Comment 6 Itamar Heim 2013-06-11 09:06:54 UTC
3.2 has been released

Comment 7 Itamar Heim 2013-06-11 09:06:54 UTC
3.2 has been released

Comment 8 Itamar Heim 2013-06-11 09:07:07 UTC
3.2 has been released

Comment 9 Itamar Heim 2013-06-11 09:35:35 UTC
3.2 has been released