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 D9A5D1FF16B for ; Tue, 29 Jul 2025 14:56:49 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 22C3A12583; Tue, 29 Jul 2025 14:58:13 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Fiona Ebner Date: Tue, 29 Jul 2025 14:57:34 +0200 Message-Id: <175379382383.4011770.3490559018193843794.b4-ty@proxmox.com> X-Mailer: git-send-email 2.39.5 In-Reply-To: <20250716124716.104765-1-f.ebner@proxmox.com> References: <20250716124716.104765-1-f.ebner@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1753793850066 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.031 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] applied: [PATCH manager stable-8+master] pve8to9: add check and script to ensure that 'keyring' option for external RBD storages is set X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" On Wed, 16 Jul 2025 14:46:59 +0200, Fiona Ebner wrote: > With the switch from QEMU's -drive to -blockdev, it is not possible > anymore to pass along the Ceph 'keyring' option via the QEMU > commandline anymore, as was previously done for externally managed RBD > storages. For such storages, it is now necessary that the 'keyring' > option is correctly configured in the storage's Ceph configuration. > > For newly created external RBD storages in Proxmox VE 9, the Ceph > configuration with the 'keyring' option is automatically added, as > well as for existing storages that do not have a Ceph configuration > at all yet. But storages that already got an existing Ceph > configuration are not automatically handled by the storage layer in > Proxmox VE 9, the check and script here covers those as well. > > [...] Applied, with a bunch of smaller follow-ups but only for some opinionated polishing, thanks! [1/1] pve8to9: add check and script to ensure that 'keyring' option for external RBD storages is set commit: 7b2ac8d295d12bb332673fa0e233da61f7ec4fdb _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel