public inbox for pdm-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Lukas Sichert <l.sichert@proxmox.com>
To: Lukas Wagner <l.wagner@proxmox.com>, pdm-devel@lists.proxmox.com
Subject: Re: [PATCH datacenter-manager v2] fix #7120: remote updates: drop vanished nodes/remotes from cache file
Date: Tue, 24 Feb 2026 16:20:59 +0100	[thread overview]
Message-ID: <b1196b7f-9fec-47e7-8843-e2d8058ee503@proxmox.com> (raw)
In-Reply-To: <20260206101914.152925-1-l.wagner@proxmox.com>

I was able to reproduce the Bug by
-removing a configured cluster from the PDM,
-deleting the cluster,
-changing the node names,
-setting up a new cluster with the same name
-adding the cluster again in PDM using the same Remote ID as before.
Now, both the old and new node names appear.
Also by manually altering the cache file and just renaming one of the
nodes, one can force the original name and the new name to show up in
the GUI.
This was tested with and without [0].

After applying this commit on top of [0], I could not reproduce the bug.

The changes look good to me.


Reviewed-by: Lukas Sichert <l.sichert@proxmox.com>
Tested-by: Lukas Sichert <l.sichert@proxmox.com>


[0]:
https://lore.proxmox.com/all/20260206094304.117465-1-l.wagner@proxmox.com/T/#u

On 2026-02-06 11:18, Lukas Wagner wrote:
> This commits makes sure that vanished remotes and remote cluster nodes
> are dropped from the remote updates cache file. This happens whenever
> the cache file is fully refreshed, either by the periodic update task,
> or by pressing "Refresh All" in the UI.
> 
> Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
> ---
> 
> Notes:
>     Changes since v1:
>       - rebased on top of the parallel fetcher changes [0] - these need to
>         be applied first!
>     
>     [0]: https://lore.proxmox.com/all/20260206094304.117465-1-l.wagner@proxmox.com/T/#u
> 
>  server/src/remote_updates.rs | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/server/src/remote_updates.rs b/server/src/remote_updates.rs
> index 2762001e..7aaacc46 100644
> --- a/server/src/remote_updates.rs
> +++ b/server/src/remote_updates.rs
> @@ -214,6 +214,11 @@ pub async fn refresh_update_summary_cache(remotes: Vec<Remote>) -> Result<(), Er
>  
>      let mut content = get_cached_summary_or_default()?;
>  
> +    // Clean out any remotes that might have been removed from the remote config in the meanwhile.
> +    content
> +        .remotes
> +        .retain(|remote, _| fetch_response.iter().any(|r| r.remote() == remote));
> +
>      for remote_response in fetch_response {
>          let remote_name = remote_response.remote().to_string();
>  
> @@ -228,6 +233,11 @@ pub async fn refresh_update_summary_cache(remotes: Vec<Remote>) -> Result<(), Er
>  
>          match remote_response.nodes() {
>              Ok(node_responses) => {
> +                // Clean out any nodes that might have been removed from the cluster in the meanwhile.
> +                entry
> +                    .nodes
> +                    .retain(|name, _| node_responses.iter().any(|n| n.node_name() == name));
> +
>                  entry.status = RemoteUpdateStatus::Success;
>  
>                  for node_response in node_responses {





      reply	other threads:[~2026-02-24 15:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-06 10:19 Lukas Wagner
2026-02-24 15:20 ` Lukas Sichert [this message]

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=b1196b7f-9fec-47e7-8843-e2d8058ee503@proxmox.com \
    --to=l.sichert@proxmox.com \
    --cc=l.wagner@proxmox.com \
    --cc=pdm-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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal