You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d67bbf2
Browse filesBrowse the repository at this point in the historyBrowse files
fix(postgres): time the plugin rollout from the write that attached it
The PluginRolledOut latch is recorded before the Cluster write that
attaches the barman-cloud plugin, and its time was used both as the
start of the rollout deadline and as the age every instance pod must
exceed to count as rolled. Now that a failing write is retried for up
to the backup deadline, the attach can come long after the latch: the
deadline was then spent before the rollout began, and a pod recreated
between the latch and the attach, without the plugin sidecar, passed
as rolled, so a Backup was created that CloudNativePG fails for good.
The latch now carries its own reason, and the write that finds the
plugin missing and attaches it re-stamps the condition, once, with the
time it was attempted. A plugin someone else attached after the latch,
another backup job or a restore, keeps the latch time: the rollout it
started can be over by the time this job writes, and its instances
would otherwise never count as rolled.
Signed-off-by: Alexey Artamonov <[email protected]>
Assisted-by: LLM
0 commit comments