Bug 1332042

Summary: VM 'down' icon moves from where it needs to be for a 'locked' vm
Product: Red Hat Enterprise Virtualization Manager Reporter: Barak Korren <bkorren>
Component: ovirt-engineAssignee: Greg Sheremeta <gshereme>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.6.5CC: gklein, gshereme, lsurette, nsimsolo, oourfali, rbalakri, Rhev-m-bugs, srevivo, tjelinek, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-13 23:02:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
screenshot none

Description Barak Korren 2016-05-01 15:14:00 UTC 
Created attachment 1152776 [details]
screenshot

Description of problem:
For a locked VM, the VM 'down' icon stays stuck to a specific window position and down not scroll with the VM row.

Version-Release number of selected component (if applicable):
3.6.5.3-0.1.el6

How reproducible:
Happens for VMs that becomes both down and locked due to BZ#1332039
Maybe in other cases as well

Additional info:
Screenshot attached
Comment 1 Tomas Jelinek 2016-05-04 10:34:54 UTC 
@Greg: I see you are assigned to https://bugzilla.redhat.com/show_bug.cgi?id=1331079 which I'd say is pretty much the same as this one. Are you working on it?
Comment 2 Greg Sheremeta 2016-05-05 13:34:42 UTC 
Not yet, but I will soon. I can take this, or you can take mine ... whichever.
Comment 3 Tomas Jelinek 2016-05-06 06:47:39 UTC 
If you have anyway planned to do it I'd pass it to you :) Thanx!
Comment 4 Greg Sheremeta 2016-05-13 23:02:32 UTC 

*** This bug has been marked as a duplicate of bug 1331079 ***
Comment 5 Tomas Jelinek 2016-05-17 07:04:32 UTC 
*** Bug 1296041 has been marked as a duplicate of this bug. ***