Bug 1085801

Summary:	Virtual machines status changes to paused after a network outage
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Roman Hodain <rhodain>
Component:	ovirt-engine	Assignee:	Nobody <nobody>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.3.0	CC:	acathrow, amureini, iheim, lpeer, michal.skrivanek, Rhev-m-bugs, rhodain, yeylon
Target Milestone:	---
Target Release:	3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-04-16 11:31:42 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 Roman Hodain 2014-04-09 12:03:22 UTC

Description of problem:
After a network outage between the RHEV-M and a hypervisor the VMs running on that hypervisor are marked as paused. When the hypervisor recovers from the connectivity issue the VMs are still running but they are still markd as paused in RHEV-M.

Version-Release number of selected component (if applicable):
rhevm-3.3.1-0.48.el6ev.noarch

How reproducible:
Not clear

Steps to Reproduce:
Not clear

Actual results:
The VMs are marked as paused, but they are running on the hypervisor

Expected results:
The VMs are marked as up when the hypervisor comes back and reports the VMs as up.

Additional info:

Comment 4 Michal Skrivanek 2014-04-14 12:33:40 UTC

can you please get the vdsm logs from src&dst showing the migration?

Comment 15 Michal Skrivanek 2014-04-15 15:42:51 UTC

an exception in guest agent socket handling is causing a silent failure during recovery on vdsm restart - setting VM status to Paused and never updating it (as the stat thread is not even started)

can you please confirm the scenario is similar/same as in bug 1082986?

Comment 17 Michal Skrivanek 2014-04-16 11:31:42 UTC

for resolution please follow bug 1052097

*** This bug has been marked as a duplicate of bug 1052097 ***