From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id A9B2D1FF141 for ; Mon, 16 Mar 2026 11:16:52 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id E8BE114FAD; Mon, 16 Mar 2026 11:17:03 +0100 (CET) From: Maximiliano Sandoval To: Fiona Ebner Subject: superseded: [PATCH qemu-server] api: qmclone: print a message with new VMID In-Reply-To: <324d2c99-dc6e-4c4e-a973-6ddbd3d1826f@proxmox.com> (Fiona Ebner's message of "Mon, 16 Mar 2026 10:35:40 +0100") References: <20260316090712.106468-1-m.sandoval@proxmox.com> <324d2c99-dc6e-4c4e-a973-6ddbd3d1826f@proxmox.com> User-Agent: mu4e 1.12.9; emacs 30.1 Date: Mon, 16 Mar 2026 10:16:29 +0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1773656149529 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.952 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 RCVD_IN_MSPIKE_H2 0.001 Average reputation (+2) RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.408 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.819 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.903 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. 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: 5AF4SUKEQ4AJACLQQ2ZPCDJ6Z7DNFI7J X-Message-ID-Hash: 5AF4SUKEQ4AJACLQQ2ZPCDJ6Z7DNFI7J X-MailFrom: m.sandoval@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 CC: pve-devel@lists.proxmox.com X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Fiona Ebner writes: > I wonder if it should rather be done at the very beginning of the task? > Then you also know what the intended ID was for a failed task, which > maybe could help with tracking left-overs from the operation. Yes, this sounds more helpful. Sent a new version. > Note that the configuration is already written after each disk, not just > at the very end. > [..] >> I think it makes sense to update the creation time too. But for now, > See: > https://bugzilla.proxmox.com/show_bug.cgi?id=6156 > https://git.proxmox.com/?p=qemu-server.git;a=commit;h=26b443c8461b3ddccffc944897af6d67a96ed7bd Good to know. Superseded-by: https://lore.proxmox.com/all/20260316101405.174423-1-m.sandoval@proxmox.com/T/#u -- Maximiliano