Bug 2010205

Summary: vm_kill_paused_time value should be determined from io_timeout
Product: [oVirt] vdsm Reporter: Milan Zamazal <mzamazal>
Component: CoreAssignee: Milan Zamazal <mzamazal>
Status: CLOSED CURRENTRELEASE QA Contact: Tamir <tamir>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.50.0CC: ahadas, bugs, mavital, tamir
Target Milestone: ovirt-4.5.0Flags: ahadas: ovirt-4.5?
Target Release: 4.50.0.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: vdsm-4.50.0.3 Doc Type: Release Note
Doc Text:
Vdsm configuration option vars.vm_kill_paused_time was removed. The corresponding value is directly dependent on the value of recently introduced sanlock.io_timeout option and needn't be configured separately.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-28 09:26:34 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 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.