fix #1842: do not pass forceStop to CT shutdown

The vm_shutdown parameter forceStop differs in behaviour between VMs
and CTs. While on VMs it ensures that a VM gets stoppped if it could
not shutdown gracefully only after the timeout passed, the container
stack always ignores any timeout if forceStop is set and hard stops
the CT immediately.
To achieve this behaviour for CTs too, the timeout is enough, as
lxc-stop then does the hard stop after timeout itself.

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>

diff --git a/src/PVE/HA/Resources/PVECT.pm b/src/PVE/HA/Resources/PVECT.pm
index 087df8128bbda66a699fedc0ea13a5ae39a9241b..a0f05f44125f5bd29ce41e8669da803297e16eba 100644 (file)
--- a/src/PVE/HA/Resources/PVECT.pm
+++ b/src/PVE/HA/Resources/PVECT.pm
@@ -83,7 +83,6 @@ sub shutdown {
        node => $nodename,
        vmid => $id,
        timeout => $shutdown_timeout,
-       forceStop => 1,
     };
 
     my $upid = PVE::API2::LXC::Status->vm_shutdown($params);