From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Christian Ebner <c.ebner@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH manager] pvestatd: improve broadcast of node version-info
Date: Thu, 27 Feb 2025 15:06:39 +0100 [thread overview]
Message-ID: <c9496ae4-711c-4fe7-8e80-72157765e8bf@proxmox.com> (raw)
In-Reply-To: <203d247f-9634-4808-a7a9-d176e39fa1cd@proxmox.com>
On 2025-01-16 17:50, Christian Ebner wrote:
> On 1/16/25 17:38, Aaron Lauterer wrote:
>>
>>
>> On 2025-01-16 17:35, Christian Ebner wrote:
>>> On 1/16/25 17:30, Aaron Lauterer wrote:
>> […]
>>> This will close issue 5894 I guess [0]?
>>>
>>> [0] https://bugzilla.proxmox.com/show_bug.cgi?id=5894
>>
>> Specifically, the 'version-info', yes. Are there other properties too?
>
> If I remember correctly all are cleared. But only the `version-info` is
> not re-broadcasted as far as I can see from a quick glance at the code.
>
> But might be worth to double check!
At least in pvestatd I didn't find any other broadcast_node_kv call
behind a similar condition that would only run it once per start of the
service.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-02-27 14:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 16:30 Aaron Lauterer
2025-01-16 16:35 ` Christian Ebner
2025-01-16 16:38 ` Aaron Lauterer
2025-01-16 16:50 ` Christian Ebner
2025-02-27 14:06 ` Aaron Lauterer [this message]
2025-01-17 12:18 ` Fiona Ebner
2025-02-26 16:02 ` Aaron Lauterer
2025-02-27 8:59 ` Fiona Ebner
2025-02-27 14:52 ` Fabian Grünbichler
2025-02-27 15:00 ` Fiona Ebner
2025-02-27 15:11 ` Fabian Grünbichler
2025-03-04 9:06 ` Thomas Lamprecht
2025-02-27 14:34 ` Aaron Lauterer
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=c9496ae4-711c-4fe7-8e80-72157765e8bf@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=c.ebner@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal