From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id F42367133E for ; Wed, 11 May 2022 11:28:58 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id F1E4019237 for ; Wed, 11 May 2022 11:28:58 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 345C41922C for ; Wed, 11 May 2022 11:28:58 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 05ACD4337C for ; Wed, 11 May 2022 11:28:58 +0200 (CEST) Date: Wed, 11 May 2022 11:28:56 +0200 From: Oguz Bektas To: Proxmox VE development discussion Message-ID: Mail-Followup-To: Oguz Bektas , Proxmox VE development discussion References: <20220511092707.155595-1-s.sterz@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220511092707.155595-1-s.sterz@proxmox.com> X-SPAM-LEVEL: Spam detection results: 0 AWL 0.515 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% 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 T_SCC_BODY_TEXT_LINE -0.01 - Subject: Re: [pve-devel] [PATCH pve-cluster] cluster config: mark qdevice end point as protected 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: , X-List-Received-Date: Wed, 11 May 2022 09:28:59 -0000 thanks for picking this up :) tested on my cluster with qdevice and it solves the issue reported in forum [0] Tested-by: Oguz Bektas [0]: https://forum.proxmox.com/threads/109308/ On Wed, May 11, 2022 at 11:27:07AM +0200, Stefan Sterz wrote: > this allows the end point to retrieve data from the qdevice properly > by leveraging pve-daemon. fixes an issue where the api would return an > empty object. > > Signed-off-by: Stefan Sterz > --- > data/PVE/API2/ClusterConfig.pm | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/data/PVE/API2/ClusterConfig.pm b/data/PVE/API2/ClusterConfig.pm > index 5a6a1ac..e7efe37 100644 > --- a/data/PVE/API2/ClusterConfig.pm > +++ b/data/PVE/API2/ClusterConfig.pm > @@ -661,6 +661,7 @@ __PACKAGE__->register_method ({ > name => 'status', > path => 'qdevice', > method => 'GET', > + protected => 1, > description => 'Get QDevice status', > permissions => { > check => ['perm', '/', [ 'Sys.Audit' ]], > -- > 2.30.2 > > > > _______________________________________________ > pve-devel mailing list > pve-devel@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel > >