From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 742C71FF0B6 for ; Thu, 12 Nov 2026 10:46:18 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 7A8F921810; Thu, 12 Nov 2026 10:44:54 +0100 (CET) From: Dominik Rusovac To: pve-devel@lists.proxmox.com Subject: [PATCH pve-ha-manager v2 14/19] manager: rename update_crs_scheduler_mod to update_crs_settings Date: Thu, 12 Nov 2026 10:44:32 +0100 Message-ID: <20261112094437.1951271-15-d.rusovac@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261112094437.1951271-1-d.rusovac@proxmox.com> References: <20261112094437.1951271-1-d.rusovac@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1794476686252 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.037 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_MED -2.3 Sender listed at https://www.dnswl.org/, medium 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: KB77PLSGXJPPACVZSZADNLWGWQIW3T2U X-Message-ID-Hash: KB77PLSGXJPPACVZSZADNLWGWQIW3T2U X-MailFrom: d.rusovac@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 List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: the method updates all CRS settings, including the automatic rebalancing options, not just the scheduler mode. rename it to avoid confusion with the CRS scheduler mode setting Signed-off-by: Dominik Rusovac --- Notes: changes since v1: * reword commit * moved before the logging patches src/PVE/HA/Manager.pm | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/PVE/HA/Manager.pm b/src/PVE/HA/Manager.pm index 7a5a685..b206719 100644 --- a/src/PVE/HA/Manager.pm +++ b/src/PVE/HA/Manager.pm @@ -94,12 +94,12 @@ sub new { # preserve disarm state across CRM master changes $self->{ms}->{disarm} = $old_ms->{disarm} if defined($old_ms->{disarm}); - $self->update_crs_scheduler_mode(); # initial set, we update it once every loop + $self->update_crs_settings(); # initial set, we update it once every loop return $self; } -sub update_crs_scheduler_mode { +sub update_crs_settings { my ($self) = @_; my $haenv = $self->{haenv}; @@ -1028,7 +1028,7 @@ sub manage { return; } - $self->update_crs_scheduler_mode(); + $self->update_crs_settings(); $self->try_persistent_group_migration(); -- 2.47.3