From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Dominik Rusovac <d.rusovac@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH ha-manager] lrm: fix typos in log messages
Date: Thu, 12 Mar 2026 09:10:02 +0100 [thread overview]
Message-ID: <311ced5c-481d-45f1-94ac-5787e4197a54@proxmox.com> (raw)
In-Reply-To: <20260312071618.15408-1-d.rusovac@proxmox.com>
Am 12.03.26 um 08:15 schrieb Dominik Rusovac:
> Signed-off-by: Dominik Rusovac <d.rusovac@proxmox.com>
> ---
> src/PVE/HA/LRM.pm | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/src/PVE/HA/LRM.pm b/src/PVE/HA/LRM.pm
> index e4b0ec8..09a965c 100644
> --- a/src/PVE/HA/LRM.pm
> +++ b/src/PVE/HA/LRM.pm
> - $haenv->log('err', "node need to be fenced - releasing agent_lock\n");
> + $haenv->log('err', "node needs to be fenced - releasing agent_lock\n");
> - "node need to be fenced during maintenance mode - releasing agent_lock\n",
> + "node needs to be fenced during maintenance mode - releasing agent_lock\n",
> - "get shutdown request in state 'lost_agent_lock' - "
> + "got shutdown request in state 'lost_agent_lock' - "
> . "detected $service_count running services",
> );
>
The fixes themselves look OK, but they all touch the log output that is
also used for regression tests, and with that come two options:
1. either it doesn't matter because no test covers these logs, which
would be rather bad on itself.
2. or, more likely, you forgot to check in the test changes required,
potentially not running the harness before sending this out.
Here it's 2., a running `make -C src/` test or building the whole package
will result in a failure to do so.
As we do not have a million of test cases and each is relatively small
line count, the churn should not be to big to send it along.
Please assemble a v2 doing so and ensure to run the the testsuite(s)
before sending any patch, a deb package build normally should do
the trick here.
next prev parent reply other threads:[~2026-03-12 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 7:16 Dominik Rusovac
2026-03-12 8:10 ` Thomas Lamprecht [this message]
2026-03-12 8:44 ` Dominik Rusovac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=311ced5c-481d-45f1-94ac-5787e4197a54@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.rusovac@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox