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

Bug 1544718

Summary:	[RFE] Improve high-availability of paused VMs due to IO error with a lease
Product:	[oVirt] ovirt-engine	Reporter:	Arik <ahadas>
Component:	BLL.Virt	Assignee:	Arik <ahadas>
Status:	CLOSED NOTABUG	QA Contact:	meital avital <mavital>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	bugs
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	rbarry: ovirt-4.5? rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
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:	2021-08-23 11:51:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Arik 2018-02-13 11:37:55 UTC

We can improve high-availability of VMs that are paused due to an IO error and are configured with a lease - we can try restarting them on other hosts (assuming there is a problem between the storage device and the particular host the VM runs on, the lease will protect us from a split-brain) and replace the resume-behavior of those VMs (that is currently set to KILL) to AUTO-RESUME.

Comment 1 Michal Skrivanek 2018-02-14 15:27:00 UTC

need to be discussed in context of bug 1540548

Comment 2 Ryan Barry 2019-01-21 14:53:43 UTC

Re-targeting to 4.3.1 since it is missing a patch, an acked blocker flag, or both

Comment 3 Michal Skrivanek 2021-08-20 08:27:40 UTC

This bug/RFE is more than 2 years old and it didn't get enough attention so far, and is now flagged as pending close. 
Please review if it is still relevant and provide additional details/justification/patches if you believe it should get more attention for the next oVirt release.

Comment 4 Arik 2021-08-23 11:51:50 UTC

Having the resume-behavior always set to KILL when a VM lease is defined renders this bz redundant - the VM will be destroyed automatically and then restarted by the engine elsewhere (also in case we have connectivity between ovirt-engine and the host)