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 8A2AC703DB for ; Fri, 6 May 2022 10:11:58 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7F591A497 for ; Fri, 6 May 2022 10:11:28 +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 0ADA3A48C for ; Fri, 6 May 2022 10:11:28 +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 CEDEC42B90 for ; Fri, 6 May 2022 10:11:27 +0200 (CEST) Message-ID: Date: Fri, 6 May 2022 10:11:27 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 Content-Language: en-US To: Thomas Lamprecht , Proxmox VE development discussion References: <20220505142709.1128710-1-m.heiserer@proxmox.com> <34ee9614-74dd-8556-3c53-84efdbeab553@proxmox.com> From: Matthias Heiserer In-Reply-To: <34ee9614-74dd-8556-3c53-84efdbeab553@proxmox.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 1.611 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 NICE_REPLY_A -3.441 Looks like a legit reply (A) 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 manager] GUI: Ceph wizard: autoselect current node 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: Fri, 06 May 2022 08:11:58 -0000 On 06.05.2022 10:00, Thomas Lamprecht wrote: > Am 5/5/22 um 16:27 schrieb Matthias Heiserer: >> www/manager6/ceph/CephInstallWizard.js | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/www/manager6/ceph/CephInstallWizard.js b/www/manager6/ceph/CephInstallWizard.js >> index 59458b0d..ebdc7f1d 100644 >> --- a/www/manager6/ceph/CephInstallWizard.js >> +++ b/www/manager6/ceph/CephInstallWizard.js >> @@ -403,6 +403,7 @@ Ext.define('PVE.ceph.CephInstallWizard', { >> name: 'mon-node', >> selectCurNode: true, >> allowBlank: false, >> + preferredValue: Proxmox.NodeName, > > That is always the local node one is connected through the web interface. > So, what if I'm connected through Node A but currently installing/initializing ceph on Node B? > Should this rather be the node currently selected in the resource tree? Well, yes, the node selector already does that. This patch only changes the behavior when installing ceph after selecting the datacenter in the GUI. In which case ceph is installed on the local node.