From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>, pdm-devel@lists.proxmox.com
Subject: Re: [RFC PATCH datacenter-manager 1/4] server: connection: multi client: use correct client error for retrying
Date: Thu, 4 Jun 2026 18:30:05 +0200 [thread overview]
Message-ID: <17a36c9d-d652-4b43-a16d-ee7bdfffac8b@proxmox.com> (raw)
In-Reply-To: <e5603a29-ff09-4796-8432-2680c8543579@proxmox.com>
On 03/06/2026 13:59, Dominik Csapak wrote:
> so of the methods we use in pve/pbs, only POST is not idempotent per
> the spec, but e.g. we can use 'PUT' for making non-idempotent changes to a vm config (for example adding a disk to a VM, this will create
> a disk and make any in the same slot unused)
>
> I'm not super sure if we can get an client error here in a way
> that would process the request with side effects on pve side and still
> trigger a retry on the pdm side, so I doubt this will make a difference
> in practice. Still wanted to mention it.
The digest-check should catch the repeated call though, as long as we
send that along, we're fine (besides maybe 1. add cfg entry, connection
fails on return but PVE processed it 2. another request deletes that cfg
immediately again 3. second retried add hits PVE and digest is again the
same; but tbh., that's an rather theoretical edge case and would require
multiple independent automation stacks interfering with each other, which
leads to odd effects in any case.
next prev parent reply other threads:[~2026-06-04 16:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 13:30 [PATCH datacenter-manager 0/4] implement back-off mechanism for Dominik Csapak
2026-05-29 13:30 ` [RFC PATCH datacenter-manager 1/4] server: connection: multi client: use correct client error for retrying Dominik Csapak
2026-05-29 23:25 ` Thomas Lamprecht
2026-06-01 7:19 ` Dominik Csapak
2026-06-03 11:48 ` Thomas Lamprecht
2026-06-03 11:59 ` Dominik Csapak
2026-06-04 16:30 ` Thomas Lamprecht [this message]
2026-05-29 13:30 ` [PATCH datacenter-manager 2/4] server: remote cache: prepare for back-off mechanism Dominik Csapak
2026-05-29 23:40 ` Thomas Lamprecht
2026-05-29 13:30 ` [PATCH datacenter-manager 3/4] server: connection: multi-client: use back-off state from remote cache Dominik Csapak
2026-05-29 13:30 ` [PATCH datacenter-manager 4/4] server: pbs client: rework to use the back-off mechanism " Dominik Csapak
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=17a36c9d-d652-4b43-a16d-ee7bdfffac8b@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@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