public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Daniel Kral <d.kral@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH ha-manager 7/7] fix #7230: resources: let shutdown api handle timeout fallback value
Date: Wed, 22 Jul 2026 16:01:49 +0200	[thread overview]
Message-ID: <20260722140149.296952-8-d.kral@proxmox.com> (raw)
In-Reply-To: <20260722140149.296952-1-d.kral@proxmox.com>

PVE::API2::LXC::Status::vm_shutdown() and PVE::API2::Qemu::vm_shutdown()
already fallback to either the configured shutdown timeout or the
default value of 60 seconds. Therefore, let the API handlers decide what
the timeout value should be set to.

This does only partially fix #7230 as HA resources are still
force-stopped as the shutdown timeout runs out.

Signed-off-by: Daniel Kral <d.kral@proxmox.com>
---
 src/PVE/HA/Resources/PVECT.pm | 10 +++++-----
 src/PVE/HA/Resources/PVEVM.pm | 10 +++++-----
 2 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/src/PVE/HA/Resources/PVECT.pm b/src/PVE/HA/Resources/PVECT.pm
index 177b9070..ead66e0e 100644
--- a/src/PVE/HA/Resources/PVECT.pm
+++ b/src/PVE/HA/Resources/PVECT.pm
@@ -87,7 +87,6 @@ sub shutdown {
     my ($class, $haenv, $id, $timeout) = @_;
 
     my $nodename = $haenv->nodename();
-    my $shutdown_timeout = $timeout // 60;
 
     my $upid;
     my $params = {
@@ -95,11 +94,12 @@ sub shutdown {
         vmid => $id,
     };
 
-    if ($shutdown_timeout) {
-        $params->{timeout} = $shutdown_timeout;
-        $upid = PVE::API2::LXC::Status->vm_shutdown($params);
-    } else {
+    # stop the CT immediately if $timeout is set to exactly 0
+    if (defined($timeout) && $timeout == 0) {
         $upid = PVE::API2::LXC::Status->vm_stop($params);
+    } else {
+        $params->{timeout} = $timeout;
+        $upid = PVE::API2::LXC::Status->vm_shutdown($params);
     }
 
     PVE::HA::Tools::upid_wait($upid, $haenv);
diff --git a/src/PVE/HA/Resources/PVEVM.pm b/src/PVE/HA/Resources/PVEVM.pm
index 87532716..d89a0bce 100644
--- a/src/PVE/HA/Resources/PVEVM.pm
+++ b/src/PVE/HA/Resources/PVEVM.pm
@@ -87,7 +87,6 @@ sub shutdown {
     my ($class, $haenv, $id, $timeout) = @_;
 
     my $nodename = $haenv->nodename();
-    my $shutdown_timeout = $timeout // 60;
 
     my $upid;
     my $params = {
@@ -95,12 +94,13 @@ sub shutdown {
         vmid => $id,
     };
 
-    if ($shutdown_timeout) {
-        $params->{timeout} = $shutdown_timeout;
+    # stop the VM immediately if $timeout is set to exactly 0
+    if (defined($timeout) && $timeout == 0) {
+        $upid = PVE::API2::Qemu->vm_stop($params);
+    } else {
+        $params->{timeout} = $timeout;
         $params->{forceStop} = 1;
         $upid = PVE::API2::Qemu->vm_shutdown($params);
-    } else {
-        $upid = PVE::API2::Qemu->vm_stop($params);
     }
 
     PVE::HA::Tools::upid_wait($upid, $haenv);
-- 
2.47.3





      parent reply	other threads:[~2026-07-22 14:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22 14:01 [PATCH-SERIES ha-manager/qemu-server 0/7] fix #7230: acknowledge configured shutdown timeout for HA resources Daniel Kral
2026-07-22 14:01 ` [PATCH qemu-server 1/7] rename config_aware_timeout to config_aware_start_timeout Daniel Kral
2026-07-22 14:01 ` [PATCH qemu-server 2/7] vm_stop: introduce config_aware_shutdown_timeout helper Daniel Kral
2026-07-22 14:01 ` [PATCH qemu-server 3/7] api: qemu: improve wording in timeout parameter descriptions Daniel Kral
2026-07-22 14:01 ` [PATCH qemu-server 4/7] api: qemu: add verbose description for shutdown and reboot timeouts Daniel Kral
2026-07-22 14:01 ` [PATCH qemu-server 5/7] fix #7230: api: vm_shutdown: make HA resources acknowledge config timeout Daniel Kral
2026-07-22 14:01 ` [PATCH qemu-server 6/7] api: vm_reboot: initialize the config-aware timeout in API handler Daniel Kral
2026-07-22 14:01 ` Daniel Kral [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260722140149.296952-8-d.kral@proxmox.com \
    --to=d.kral@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal