Bug 2010205 - vm_kill_paused_time value should be determined from io_timeout
Summary: vm_kill_paused_time value should be determined from io_timeout
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Core
Version: 4.50.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ovirt-4.5.0
: 4.50.0.3
Assignee: Milan Zamazal
QA Contact: Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-04 07:55 UTC by Milan Zamazal
Modified: 2022-04-28 09:26 UTC (History)
4 users (show)

Fixed In Version: vdsm-4.50.0.3
Clone Of:
Environment:
Last Closed: 2022-04-28 09:26:34 UTC
oVirt Team: Virt
Embargoed:
ahadas: ovirt-4.5?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-43749 0 None None None 2021-10-04 08:00:48 UTC
oVirt gerrit 117523 0 master MERGED virt: Derive VM kill timeout from io_timeout 2021-11-18 13:54:21 UTC

Description Milan Zamazal 2021-10-04 07:55:03 UTC
Vdsm sanlock I/O timeout value is now configurable (see sanlock:io_timeout option) and is documented in io_timeouts.md. vm_kill_paused_time option default value for killing VMs with leases still matches io_timeout default value, but if io_timeout is changed then the vm_kill_paused_time must be adjusted accordingly.

There is no need to keep vm_kill_paused_time option since its correct value directly depends on io_timeout value. The corresponding value should be computed and applied automatically.

Comment 3 Sandro Bonazzola 2022-04-28 09:26:34 UTC
This bugzilla is included in oVirt 4.5.0 release, published on April 20th 2022.

Since the problem described in this bug report should be resolved in oVirt 4.5.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.