From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id 265FE1FF0B6 for ; Thu, 12 Nov 2026 12:52:22 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 7535321903; Thu, 12 Nov 2026 12:50:22 +0100 (CET) From: Fiona Ebner To: pve-devel@lists.proxmox.com Subject: [PATCH container v7 18/32] migrate: add 'skip-config-check' property Date: Thu, 12 Nov 2026 12:48:50 +0100 Message-ID: <20261112115001.107306-19-f.ebner@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261112115001.107306-1-f.ebner@proxmox.com> References: <20261112115001.107306-1-f.ebner@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1794484205886 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.268 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: RWA6FN56VKXLGI7WPRSYO6SG6LIG52CE X-Message-ID-Hash: RWA6FN56VKXLGI7WPRSYO6SG6LIG52CE X-MailFrom: f.ebner@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: With pve-guest-common commit "abstract migrate: intra-cluster: check config can be parsed on target", there now is a check to see if the configuration file can be parsed on the target node, so there should be a way to opt-out as an escape hatch. Signed-off-by: Fiona Ebner --- Changes in v7: * Use factored out helper from guest-common. src/PVE/API2/LXC.pm | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/src/PVE/API2/LXC.pm b/src/PVE/API2/LXC.pm index 993f62a..faab9f3 100644 --- a/src/PVE/API2/LXC.pm +++ b/src/PVE/API2/LXC.pm @@ -82,12 +82,23 @@ my $migrate_json_properties = { minimum => '0', default => 'migrate limit from datacenter or storage config', }, + 'skip-config-check' => { + type => 'boolean', + optional => 1, + default => 0, + description => + 'For intra-cluster migration. Skip checking if the configuration can be parsed' + . ' successfully by the target. Using this flag can lead to ignored' + . ' configuration options if the target is too old to parse them.', + }, }; # Properties that will be forwarded via the HA stack to the LRM, which will then use them for its # own invocation of the migration API endpoint. The other properties are not forwarded and lost for # HA migrations with many being hard-coded for the LRM invocation. -my $ha_migrate_props = {}; +my $ha_migrate_props = { + 'skip-config-check' => 1, +}; sub ha_migrate_json_properties { my $forwarded_props = {}; -- 2.47.3