Bug 2080208

Summary:	Stuck migration is hard to debug
Product:	Container Native Virtualization (CNV)	Reporter:	Fabian Deutsch <fdeutsch>
Component:	Virtualization	Assignee:	sgott
Status:	CLOSED DUPLICATE	QA Contact:	Kedar Bidarkar <kbidarka>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.10.0	CC:	cnv-qe-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-04-29 09:08:56 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 Fabian Deutsch 2022-04-29 09:05:50 UTC

Description of problem:
Some migration details are in the logs, but not sufficient to debug i.e. timeouts.

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
https://github.com/oVirt/vdsm/blob/master/lib/vdsm/virt/migration.py#L1024 is an example with details which can help to understand why/if a migration is stuck.
The ask is to provide the same details in periodic live migratin messages.

Comment 1 Fabian Deutsch 2022-04-29 09:08:56 UTC


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