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

Bug 890495

Summary: Wrong general information for the selected VM
Product: [Retired] oVirt Reporter: Alex Leonhardt <alex.tuxx>
Component: ovirt-engine-webadminAssignee: Einav Cohen <ecohen>
Status: CLOSED WORKSFORME QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.1 GACC: acathrow, dyasny, ecohen, iheim, mgoldboi, ykaul
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: 2012-12-31 13:23:59 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
Screenshot none

Description Alex Leonhardt 2012-12-27 10:11:15 UTC
Created attachment 669560 [details]
Screenshot

Description of problem:

The Detail frame for a VM is showing the wrong information for a selected VM instead of the selected one. 

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

ovirt-engine 3.1

ovirt-engine-webadmin-portal.noarch
                        3.1.0-3.19.el6  @ovirt31-dre                            


How reproducible:

Everytime

Steps to Reproduce:
1. Login to webadmin console
2. Select a System
3. Select Virtual Machines
4. Select a VM
5. In bottom frame, go to "General" 

Unsure of how exactly this is reproduced as it seems to randomly select a host ? I've started up serveral hosts since, but it keeps showing that one VM in the detail page - may be the last created VM ? 


Actual results:

The general detail page does not show the details of the VM selected. 

Expected results:

Details of selected VM.

Additional info:

Screenshot attached.

Comment 1 Alex Leonhardt 2012-12-31 13:23:59 UTC
I've added some more VMs and the issue is no longer reproducable. May just have been a hiccup or a browser issue (?).