Bug 1258659

Summary:	[RFE] provide better monitoring to allow to know to which disk the VM is writing to after failed live snapshot.
Product:	[oVirt] ovirt-engine	Reporter:	Christopher Pereira <kripper>
Component:	RFEs	Assignee:	Daniel Erez <derez>
Status:	CLOSED WONTFIX	QA Contact:	Avihai <aefrat>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	---	CC:	bugs, lsurette, michal.skrivanek, srevivo, tnisan, ykaul
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	ylavi: ovirt-future? ylavi: planning_ack? ylavi: devel_ack? ylavi: testing_ack?
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-19 14:18:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1018867

Description Christopher Pereira 2015-08-31 23:57:11 UTC

== Description of problem ==

A failed snapshot creation or LSM (Live Storage Migration) requires the VM to be restarted.

The logs display:

"Failed to create live snapshot 'Auto-generated for Live Storage Migration' for VM 'test-vm'. VM restart is recommended."

It's nice to have this bug showing this hint, but restarting a VM because of a temporary network problem while doing a LSM is not affordable in production.

== How reproducible ==

Easy to reproduce.

== Steps to Reproduce ==

1. Configure host to fail during snapshot creation (we need to reproduce a "Failed to create live snapshot 'Auto-generated for Live Storage Migration' for VM 'XXXXXX'. VM restart is recommended." warning).
2. Create a snapshot (process must fail)
3. Check snapshots and compare with virsh output

== Actual results ==

Current snapshot displayed inside oVirt is wrong.
Check real active snapshot via virsh.
Workarround is to restart the VM.

== Expected results ==

oVirt must show correct results, without requiring a VM restart.

== Additional info ==

See: https://bugzilla.redhat.com/show_bug.cgi?id=1018867

Comment 1 Allon Mureinik 2015-09-01 12:59:37 UTC

When a live snapshost fails, we should query QEMU and adjust engine/vdsm's definition of the VM to match the "real" definition.

Comment 2 Tal Nisan 2019-11-19 14:18:43 UTC

This is an old RFE I don't think we will get to it since we haven't so far given capacity issues, if somehow it's really important for someone please reopen.