Bug 966120

Summary:	Guest Memory Utilzation not showing in Admin Console and Reports
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Allie DeVolder <adevolder>
Component:	ovirt-engine-webadmin-portal	Assignee:	Michal Skrivanek <michal.skrivanek>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	medium	Docs Contact:
Priority:	high
Version:	3.1.0	CC:	acathrow, adevolder, byount, ecohen, iheim, michal.skrivanek, Rhev-m-bugs, ykaul
Target Milestone:	---
Target Release:	3.3.0
Hardware:	All
OS:	Linux
Whiteboard:	virt
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-03 10:17:58 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:

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.