From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH container] remote migration: mtunnel: fix call to destroy config in error case
Date: Mon, 9 Nov 2026 14:52:18 +0100 [thread overview]
Message-ID: <20261109135320.153065-1-f.ebner@proxmox.com> (raw)
The PVE::LXC::destroy_config() function does not exist.
Fixes: 0e0958a ("migration: add remote migration")
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
src/PVE/API2/LXC.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/PVE/API2/LXC.pm b/src/PVE/API2/LXC.pm
index 63d30d1..d736dac 100644
--- a/src/PVE/API2/LXC.pm
+++ b/src/PVE/API2/LXC.pm
@@ -3433,7 +3433,7 @@ __PACKAGE__->register_method({
warn "Removing temporary VM config..\n";
$run_locked->(sub {
- PVE::LXC::destroy_config($state->{vmid});
+ PVE::LXC::Config->destroy_config($state->{vmid});
});
die "Exiting mtunnel\n";
--
2.47.3
next reply other threads:[~2026-11-09 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 13:52 Fiona Ebner [this message]
2026-11-09 14:31 ` [PATCH container] remote migration: mtunnel: fix call to destroy config in error case Fabian Grünbichler
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=20261109135320.153065-1-f.ebner@proxmox.com \
--to=f.ebner@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