Bug 966120 - Guest Memory Utilzation not showing in Admin Console and Reports
Summary: Guest Memory Utilzation not showing in Admin Console and Reports
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.1.0
Hardware: All
OS: Linux
high
medium
Target Milestone: ---
: 3.3.0
Assignee: Michal Skrivanek
QA Contact: Pavel Stehlik
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-22 14:18 UTC by Allie DeVolder
Modified: 2018-12-01 14:54 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-03 10:17:58 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Allie DeVolder 2013-05-22 14:18:38 UTC
Description of problem:
Guest Memory Utilzation not showing in Admin Console and Reports

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

How reproducible:
Unknown

Steps to Reproduce:
1. Create a Windows 7 vm and install rhev-tools-3.1-9 or whatever the current one is
2. Sysprep seal that vm and turn it into a template
3. Create a pool of 200 VMs from that template and power them on 10 at a time so they sysprep

Actual results:
After a certain period of time or a certain number of VMs started (undetermined), the AdminPortal will no longer report memory statistics for the VMs

Expected results:
Memory statistics for VMs continually reported.

Comment 1 Michal Skrivanek 2013-05-27 06:59:13 UTC
no logs, no version info.

In the case I see 2 different instances of this, one where all VMs are missing IPs (likely the socket reconnection issue we've seen in 3.1.z) and another one about vdagent - which doesn't have anything to do with the IP reported.

Comment 2 Michal Skrivanek 2013-05-27 07:10:12 UTC
is this the same thing as bug 967136?

Comment 3 Michal Skrivanek 2013-07-03 10:17:58 UTC
lacking enough logs it's hard to confirm for sure, but most likely the issue is addressed by reconnect fixes in 3.1.z and a fix of channel fd closing in 3.2

Comment 4 Bryan Yount 2013-07-18 00:39:28 UTC
Actually, we later found out it was bug 972749 which has now been resolved. Thanks.


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