From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id F3E1B1FF133 for ; Mon, 11 May 2026 16:28:13 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id DB63C1CB56; Mon, 11 May 2026 16:28:11 +0200 (CEST) From: Fiona Ebner To: pve-devel@lists.proxmox.com, Daniel Herzig Subject: applied: [PATCH container] fix #7568: ensure new vmid in pve ipams when cloning containers Date: Mon, 11 May 2026 16:27:40 +0200 Message-ID: <177850965695.179934.10082658491703986079.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260507112341.268585-1-d.herzig@proxmox.com> References: <20260507112341.268585-1-d.herzig@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1778509575696 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.009 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment 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: JTIJGDWOTSBFHE3377K5V22GFM2IEVRN X-Message-ID-Hash: JTIJGDWOTSBFHE3377K5V22GFM2IEVRN 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: On Thu, 07 May 2026 13:23:41 +0200, Daniel Herzig wrote: > This patch addresses the incorrect application of the original > vmid to cloned containers in pve ipams, which results in duplicate > vmid entries in the `/cluster/sdn/ipams/pve/status` endpoint. Applied, thanks! [1/1] fix #7568: ensure new vmid is used for ipams when cloning containers commit: d7f0f988897c4d50830992336b51b365e1913731