Bug 1544718 - [RFE] Improve high-availability of paused VMs due to IO error with a lease
Summary: [RFE] Improve high-availability of paused VMs due to IO error with a lease
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Arik
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-13 11:37 UTC by Arik
Modified: 2021-08-23 11:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-23 11:51:50 UTC
oVirt Team: Virt
Embargoed:
rbarry: ovirt-4.5?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1540548 0 high CLOSED [RFE] Automatically restart HA VMs paused due to I/O Error 2021-09-09 13:09:55 UTC

Internal Links: 1540548

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)
Note You need to log in before you can comment on or make changes to this bug.