From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40])
	by lore.proxmox.com (Postfix) with ESMTPS id 85F1E1FF138
	for <inbox@lore.proxmox.com>; Mon, 20 Jul 2026 13:14:41 +0200 (CEST)
Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1])
	by gate001.proxmox.com (Proxmox) with ESMTP id BA89A21522;
	Mon, 20 Jul 2026 13:14:19 +0200 (CEST)
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com,
	Daniel Kral <d.kral@proxmox.com>
Subject: applied: [PATCH-SERIES network 0/2] assert vnet zone exists on create
 and update
Date: Mon, 20 Jul 2026 13:13:47 +0200
Message-ID: <178454602804.2519483.12231304129345615981.b4-ty@b4>
X-Mailer: git-send-email 2.47.3
In-Reply-To: <20260703104750.117988-1-d.kral@proxmox.com>
References: <20260703104750.117988-1-d.kral@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: 1784546011794
X-SPAM-LEVEL: Spam detection results:  0
	AWL                     0.230 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_LOW        -0.7 Sender listed at https://www.dnswl.org/,
 low 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: 4PX5B273MQTIXQOMYPTYDTG4REQPQN7L
X-Message-ID-Hash: 4PX5B273MQTIXQOMYPTYDTG4REQPQN7L
X-MailFrom: t.lamprecht@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 <pve-devel.lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Owner: <mailto:pve-devel-owner@lists.proxmox.com>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Subscribe: <mailto:pve-devel-join@lists.proxmox.com>
List-Unsubscribe: <mailto:pve-devel-leave@lists.proxmox.com>

On Fri, 03 Jul 2026 12:47:48 +0200, Daniel Kral wrote:
> If a VNet is created or updated with an empty zone '' or a non-existing
> zone identifier, the API handler will die with a slighly confusing error
> message:
> 
> create sdn vnet object failed: cannot lookup undefined type! at
> /usr/share/perl5/PVE/API2/Network/SDN/Vnets.pm line 326.
> 
> [...]

Applied, thanks!

[1/2] prefix specific sdn resource type to existence assertion string
      commit: 748c4204d3cffbd406fe69d0120b7db536ad1a12
[2/2] api: vnets: assert vnet zone exists on create and update
      commit: fa8f888541568b7c5d01bdec6e60d81657656a8b