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

Bug 1136982

Summary:	vdsClient is not showing the correct information of the VM
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Udayendu Sekhar Kar <ukar>
Component:	vdsm	Assignee:	Vinzenz Feenstra [evilissimo] <vfeenstr>
Status:	CLOSED ERRATA	QA Contact:	Nisim Simsolo <nsimsolo>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.4.1-1	CC:	bazulay, ecohen, frantisek.dvorak01, iheim, lpeer, michal.skrivanek, nyechiel, ofrenkel, pstehlik, rpai, ukar, yeylon
Target Milestone:	---	Keywords:	ZStream
Target Release:	3.5.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	virt
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously, a naming issue caused a permanent communication disruption with certain guest virtual machines until the complete stop and restart of the affected virtual machine. This problem has been now resolved.	Story Points:	---
Clone Of:
Clones:	1150503 (view as bug list)		Environment:
Last Closed:	2015-02-11 21:12:24 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:
Bug Depends On:
Bug Blocks:	1126430, 1150503

Description Udayendu Sekhar Kar 2014-09-03 18:43:04 UTC

Description of problem:
vdsClient is not showing all the guest names but using 'virsh' its possible to get all the vm's name. In all the guest VM rhevm-guest-agent package is installed and service is running.

If "#vdsClient -s 0 getAllVmStats |grep guestName" is showing 8 vm's name, "virsh -r list" is showing 18 which is the actual number of vms running on that host.

Version-Release number of selected component (if applicable):
hypervisor (20140725.0.el6ev)

How reproducible:
Not sure

Steps to Reproduce:
1.
2.
3.

Actual results:
vdsClient is now showing the actul number of VMs running on the hypervisor.

Expected results:
vdsClient should show the equal number of VMs as virsh as rhevm-guest-agent is already installed in the VMs.

Comment 1 Omer Frenkel 2014-09-04 06:14:22 UTC

guestName is the vm hostname, and reported only if ovirt guest agent installed.
Can you please check for one of the vms, where guest agent is running but guestName is not reported, what is the OS and what version of guest agent is installed?

Comment 2 Vinzenz Feenstra [evilissimo] 2014-09-04 09:34:17 UTC

Just FYI: The correct query to check how many vms are there should rather be 

# vdsClient -s 0 list ids | wc -l
# virsh -r list | grep "running" | wc -l


Other than that I second omers request. Please check the vms where the guestName is missing and please report OS & OS Version & guest agent status & guest agent version.

Comment 3 Frantisek Dvorak 2014-09-10 09:57:42 UTC

Hello we use vdsClient command to monitore which vm are run on which hypervisor. And if I restart vdsmd vdsClient it stop getting some data (like guestname, ip addresses and so on) until I migrate vm out and back to the hypervisor.


On guest there ade agent installed and running:

yum list installed | grep guest
rhevm-guest-agent-common.noarch    1.0.8-6.el6ev           @rhel-x86_64-rhev-agent-6-server

service ovirt-guest-agent status
ovirt-guest-agent (pid  2811) is running...

hypervisor: Red Hat Enterprise Virtualization Hypervisor release 6.5 (20140725.0.el6ev)

vdsClient -s 0 list ids | wc -l
14

virsh -r list | grep "running" | wc -l
14

vdsClient -s 0 getAllVmStats |grep guestName | wc -l
12

vdsClient return needed data only form some vm's even there are guest agent running

Comment 4 Frantisek Dvorak 2014-09-16 10:43:02 UTC

Information about vm that don't display info in hypervisor using vdsClient.

Red Hat Enterprise Linux Server release 6.3 (Santiago)
rhevm-guest-agent-common.noarch    1.0.8-6.el6ev           @rhel-x86_64-rhev-agent-6-server

service ovirt-guest-agent status
ovirt-guest-agent (pid  2811) is running...

Comment 6 Vinzenz Feenstra [evilissimo] 2014-09-23 08:18:46 UTC

(In reply to Frantisek Dvorak from comment #4)
> Information about vm that don't display info in hypervisor using vdsClient.
> 
> Red Hat Enterprise Linux Server release 6.3 (Santiago)
> rhevm-guest-agent-common.noarch    1.0.8-6.el6ev          
> @rhel-x86_64-rhev-agent-6-server
> 
> service ovirt-guest-agent status
> ovirt-guest-agent (pid  2811) is running...

Mr Dvorak, could you please report the vdsm version on the hypervisor?
(rpm -q vdsm)


Considering the hypervisor build is from July 2014, I am assuming that you're using RHEVM 3.4? Is that correct?

Thanks.

Comment 7 Frantisek Dvorak 2014-09-23 08:23:42 UTC

Hello hypervisor  vdsm version: vdsm-4.14.11-5.el6ev.x86_64
Yes we are using now RHEV Version 3.4.2-0.2.el6ev 

Thanks for investigation

FD

Comment 8 Michal Skrivanek 2014-09-25 14:49:54 UTC

I suppose the vdsm.log from the host would help. We need to capture the time before and after the restart.
Also please specify at least one of the VM which is not showing up afterwards

Please send to me,Uday,and Vinzenz directly

Comment 9 Michal Skrivanek 2014-10-07 07:59:58 UTC

found the issue in VM recovery flow, fix is simple and we'll backport it as far back as we can

Comment 12 Nisim Simsolo 2014-10-22 11:02:45 UTC

Verified using next components:
Host:
vdsm-4.16.5-2.el6ev.x86_64
libvirt-0.10.2-46.el6.x86_64
sanlock-2.8-1.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.448.el6.x86_64
Engine:
rhevm-3.5.0-0.14.beta.el6ev.noarch

Comment 14 errata-xmlrpc 2015-02-11 21:12:24 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0159.html