From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
	by lore.proxmox.com (Postfix) with ESMTPS id 0E1011FF164
	for <inbox@lore.proxmox.com>; Fri, 28 Feb 2025 09:46:36 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id 7FA048471;
	Fri, 28 Feb 2025 09:46:32 +0100 (CET)
Message-ID: <78a9d61a-c1c3-47d7-93fd-13399cfd6fc3@proxmox.com>
Date: Fri, 28 Feb 2025 09:46:24 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
 Daniel Kral <d.kral@proxmox.com>
References: <20250211160825.254167-1-d.kral@proxmox.com>
Content-Language: en-US
From: Fiona Ebner <f.ebner@proxmox.com>
In-Reply-To: <20250211160825.254167-1-d.kral@proxmox.com>
X-SPAM-LEVEL: Spam detection results:  0
 AWL -0.044 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_VALIDITY_CERTIFIED_BLOCKED 0.001 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.001 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.001 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
Subject: [pve-devel] partially-applied: [PATCH container/qemu-server/storage
 v2 00/31] consistent assertions for volume's content types
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>

Am 11.02.25 um 17:07 schrieb Daniel Kral:
> qemu-server:
> 
> Daniel Kral (15):
>   test: cfg2cmd: expect error for invalid volume's storage content type
>   fix #5284: api: move-disk: assert content type support for target storage
>   fix #5284: api: clone_vm: assert content type support for target storage
>   api: remove unused size variable in check_storage_access

Applied the above 4 patches now, squashing in adding a 'content' key for
the test case. Thanks!

>   api: remove unusable default storage parameter in check_storage_access
>   fix #5284: api: update-vm: assert content type support for cloudinit images
>   fix #5284: cli: importovf: assert content type support for target storage
>   tree-wide: update vdisk_alloc optional arguments signature
>   cfg2cmd: improve error message for invalid volume content type
>   api: {clone,move}_vm: use volume content type assertion helpers
>   api: {create,update}_vm: use volume content type assertion helpers
>   api: import{disk,ovf}: use volume content type assertion helpers
>   api: qmrestore: use volume content type assertion helpers
>   api: migrate_vm: use volume content type assertion helpers
>   tree-wide: add todos for breaking content type assertions


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel