Bug 1332042 - VM 'down' icon moves from where it needs to be for a 'locked' vm
Summary: VM 'down' icon moves from where it needs to be for a 'locked' vm
Keywords:
Status: CLOSED DUPLICATE of bug 1331079
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.6.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Greg Sheremeta
QA Contact: meital avital
URL:
Whiteboard:
: 1296041 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-01 15:14 UTC by Barak Korren
Modified: 2016-05-17 07:04 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-13 23:02:32 UTC
oVirt Team: Virt
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot (130.91 KB, image/png)
2016-05-01 15:14 UTC, Barak Korren
no flags Details

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. ***


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